1
00:00:00,000 --> 00:00:14,320
This is Hacker Public Radio Episode 3,871 from Monday 5 June 2023.

2
00:00:14,320 --> 00:00:20,280
Today's show is entitled, HPR Community News from May 2023.

3
00:00:20,280 --> 00:00:24,120
It is part of the series HPR Community News.

4
00:00:24,120 --> 00:00:29,720
It is hosted by HPR volunteers and is about 94 minutes long.

5
00:00:29,720 --> 00:00:32,480
It carries an explicit flag.

6
00:00:32,480 --> 00:00:39,120
The summary is, HPR volunteers Rindave Retro and can't talk about shows released and

7
00:00:39,120 --> 00:00:41,800
comments posted in May 2023.

8
00:00:41,800 --> 00:00:47,480
Hi everybody, my name is Ken Falun and you're listening to another episode of Hacker Public

9
00:00:47,480 --> 00:00:48,480
Radio.

10
00:00:48,480 --> 00:00:55,840
Today is HPR Community News from May 2023, heart-to-believe it's May already guys.

11
00:00:56,400 --> 00:01:02,120
Joining me tonight in alphabetical order is starting from the top is Dave.

12
00:01:02,120 --> 00:01:07,400
Dave Morris, close my name again to the D and yes hello everybody.

13
00:01:07,400 --> 00:01:14,880
Then we have all the way from a Mary Kay with that be Rind from Baltimore that if

14
00:01:14,880 --> 00:01:22,440
you're Mary Kay wouldn't that is America and then we have Retro hi this is Rito from

15
00:01:22,520 --> 00:01:23,960
Switzerland.

16
00:01:23,960 --> 00:01:31,520
Yeah, my last time was more than a year ago on a new year's show when I went to join

17
00:01:31,520 --> 00:01:32,520
again.

18
00:01:32,520 --> 00:01:33,520
Excellent.

19
00:01:33,520 --> 00:01:34,880
Excellent.

20
00:01:34,880 --> 00:01:41,040
This is HPR which is Hacker Public Radio, a podcast where the shows are contributed

21
00:01:41,040 --> 00:01:49,560
by a random weirdos on the internet that's a t-shirt right there and we have been doing

22
00:01:49,560 --> 00:01:51,080
this for quite a while.

23
00:01:51,080 --> 00:01:56,920
Now and we need to, well it's a cool idea so if you're interested in keeping a goal

24
00:01:56,920 --> 00:02:04,360
submit a show once your year is all we're asking for people and this show is around

25
00:02:04,360 --> 00:02:10,520
up a podspin going on in the community over the last month and what a busy month it's been

26
00:02:10,520 --> 00:02:15,720
Dave as and we have a new host.

27
00:02:15,760 --> 00:02:22,720
This is where Dave introduced the new host, Caddy's breaking from the script, go out.

28
00:02:22,720 --> 00:02:24,880
It's all right, it's all right.

29
00:02:24,880 --> 00:02:30,160
Yes we have a new host whose name I didn't double check with the pronunciation but I'm

30
00:02:30,160 --> 00:02:38,160
going to go for Rionokey, sort of a Japanese style name so yeah welcome on board.

31
00:02:38,160 --> 00:02:43,800
Always, always nice to hear to have new host joining.

32
00:02:43,800 --> 00:02:48,360
It is excellent but I'd also like to see some of the older hosts come back that would

33
00:02:48,360 --> 00:02:50,560
be also excellent news.

34
00:02:50,560 --> 00:02:56,400
Anyway this show what we normally do is we go through all the shows for the previous

35
00:02:56,400 --> 00:03:07,120
month that way for people who only subscribe to this feed, know what is unauthor and can

36
00:03:07,120 --> 00:03:12,720
select a like heart and then we basically through the mailing list and anything else that's

37
00:03:12,760 --> 00:03:16,160
been happening around the juncture, just a little bit.

38
00:03:16,160 --> 00:03:25,400
First show last month was episode 3,846, which we are a community news for April 2023.

39
00:03:25,400 --> 00:03:26,960
And the one you were on.

40
00:03:26,960 --> 00:03:28,960
This was your show, wasn't it?

41
00:03:28,960 --> 00:03:29,960
I did.

42
00:03:29,960 --> 00:03:36,840
Yes, yes, it's a ruin and I did that one, thanks Rionokey, I hope you got that was screaming

43
00:03:36,840 --> 00:03:42,680
down the microphone that you guys know, that's not fine.

44
00:03:43,120 --> 00:03:45,400
Now I can't remember what it was to cover my soul work up.

45
00:03:48,840 --> 00:03:50,440
You should have recorded the show again.

46
00:03:50,440 --> 00:03:53,080
I should have to go back and listen to it.

47
00:03:53,080 --> 00:04:01,520
Let me see if I can read from the transcripts, but I didn't say anything controversial

48
00:04:01,520 --> 00:04:03,600
as nobody was commenting.

49
00:04:03,600 --> 00:04:09,360
Let's go on to the next, which is all of some of the tell me what that is, synchotron.

50
00:04:10,320 --> 00:04:16,680
Yep, this is a show about shows coming up by extension Roy, and I'm looking forward

51
00:04:16,680 --> 00:04:20,240
to that series again, no comments on that.

52
00:04:20,240 --> 00:04:26,960
And editing Thunderbird email filters using them now, this was something that I didn't

53
00:04:26,960 --> 00:04:32,120
know you could do in the first place and be, I didn't know you could do with them.

54
00:04:32,120 --> 00:04:35,600
There was one comment, did you want to read that?

55
00:04:35,600 --> 00:04:39,320
Yes, so it's from the end.

56
00:04:39,320 --> 00:04:43,640
Yeah, the host himself, some guy on the internet lives, dreamed the process, he says.

57
00:04:43,640 --> 00:04:49,360
I've also streamed a Thunderbird client config and the VIM filter editing on YouTube,

58
00:04:49,360 --> 00:04:57,200
CC by SA, the VIM editing starts around 1 hour, 11, and it's 35 in the video.

59
00:04:57,200 --> 00:05:04,440
Wow, he's put some time into that one, I haven't looked, I didn't know you could do this

60
00:05:04,440 --> 00:05:10,440
because I do it, and I wrote a project that manages them as well, so you don't accidentally

61
00:05:10,440 --> 00:05:18,000
go and splat your changes onto the live thing, although Scottie was very cautious about

62
00:05:18,000 --> 00:05:21,440
how he did it as well, so good stuff.

63
00:05:21,440 --> 00:05:27,000
I was quite surprised that email is still such a big thing for somebody at home.

64
00:05:27,000 --> 00:05:34,400
Yes, yes, it's the last bastion, unfortunately, it seems to be almost impossible

65
00:05:34,400 --> 00:05:38,680
to run your own server now, but that's actually what I'm just about to roll and let's take

66
00:05:38,680 --> 00:05:40,680
it off first.

67
00:05:40,680 --> 00:05:52,320
I can't see there's any, there are features of email that are not duplicated elsewhere.

68
00:05:52,320 --> 00:05:57,600
The fact that it remains for as long as you want it to remain, it doesn't vanish or disappear

69
00:05:57,600 --> 00:06:05,640
in some giant list that you can't find as with other instances, other vaguely comparable

70
00:06:05,640 --> 00:06:07,640
things.

71
00:06:07,640 --> 00:06:12,360
You can also receive an email and take action on it relatively easily.

72
00:06:12,360 --> 00:06:18,480
I certainly do in Thunderbird, I get it, runs scripts for me, if I get messages and stuff

73
00:06:18,480 --> 00:06:26,120
of certain types, and you can order it and format it and do all the manner of good things.

74
00:06:26,360 --> 00:06:30,160
I can't see that it's ever going to totally go away.

75
00:06:30,160 --> 00:06:32,160
I hope not.

76
00:06:32,160 --> 00:06:38,520
The following day, we had troubleshooting, don't overlook the obvious from Brian and Ohio,

77
00:06:38,520 --> 00:06:44,800
now that this one was dripping with hard, hard sauce experience.

78
00:06:44,800 --> 00:06:46,800
What'd you think?

79
00:06:46,800 --> 00:06:47,800
Trying to remember what it was.

80
00:06:47,800 --> 00:06:52,240
Oh, yeah, he was, wow, he was just a very good one.

81
00:06:52,280 --> 00:06:57,280
Is this the one where he bought parts during the investigation, what is wrong?

82
00:06:57,280 --> 00:06:58,280
Yep, that's all.

83
00:06:58,280 --> 00:07:04,720
Yeah, I thought he did a magnificent job and his explanation was really, really good.

84
00:07:04,720 --> 00:07:11,680
And also, how to make sure that you don't file under these circumstances, if you've looked

85
00:07:11,680 --> 00:07:14,800
to everything and not found the answer, really good.

86
00:07:14,800 --> 00:07:19,000
There are some comments, are you on a roller or a retro?

87
00:07:19,000 --> 00:07:22,080
Do you want to read Kevin O'Royan's comment there?

88
00:07:22,080 --> 00:07:24,600
I can read Kevin O'Brien's.

89
00:07:24,600 --> 00:07:30,440
So first comment, from Kevin O'Brien, good advice.

90
00:07:30,440 --> 00:07:31,600
Thanks for some good advice.

91
00:07:31,600 --> 00:07:37,680
I have several misbehaving computers I need to fix, and your reminder is thus very timely.

92
00:07:37,680 --> 00:07:40,440
And Jill says, troubleshooting is a part.

93
00:07:40,440 --> 00:07:46,240
I do agree with your last statement that haste makes waste, which leads to jumping to conclusions

94
00:07:46,320 --> 00:07:50,800
and not getting the results you expected leading to frustration.

95
00:07:50,800 --> 00:07:53,600
You usually have to follow your goals as they say.

96
00:07:53,600 --> 00:08:00,560
First impressions, previous experience related to the given topic and the right state of mind

97
00:08:00,560 --> 00:08:03,280
can lead you to the correct answer quickly.

98
00:08:03,280 --> 00:08:08,640
There are particular steps you mentioned, you have to walk through in your mind

99
00:08:08,640 --> 00:08:12,400
and testing your assumptions to see if you're on the right track.

100
00:08:12,480 --> 00:08:18,640
The old adage, the failure is the best teacher to learn from and improve your skills

101
00:08:18,640 --> 00:08:19,920
whatever they may be.

102
00:08:19,920 --> 00:08:26,000
Great episode, get people to implement critical thinking skills and enjoy the experience.

103
00:08:26,000 --> 00:08:27,680
Good show.

104
00:08:27,680 --> 00:08:32,320
So the next one was a continuation of a Hukas travel series.

105
00:08:32,320 --> 00:08:35,440
This is something I personally requested him to do.

106
00:08:35,440 --> 00:08:40,880
I like the show where he and his good wife are going around America.

107
00:08:40,880 --> 00:08:44,960
And we are proxying along with him.

108
00:08:44,960 --> 00:08:48,720
There are loads of pictures in the show notes as well.

109
00:08:48,720 --> 00:08:52,640
And Rachael, do you want to have a goal of these little comments?

110
00:08:52,640 --> 00:08:55,200
Or would you prefer to lead the truth?

111
00:08:55,200 --> 00:08:57,440
I can drive, it plays with me.

112
00:08:57,440 --> 00:09:04,000
So the first common is by Staché, AF, space museum.

113
00:09:04,000 --> 00:09:08,960
I'm surprised you didn't stop by the space history museum and tour

114
00:09:09,040 --> 00:09:11,600
of the Gene Roddenberry exhibit.

115
00:09:11,600 --> 00:09:16,320
It's strange hearing someone talking about things to do nearby and thinking

116
00:09:16,320 --> 00:09:17,760
what's the idea of when they were?

117
00:09:18,800 --> 00:09:19,440
Oh, cool.

118
00:09:20,480 --> 00:09:21,440
My turn.

119
00:09:21,440 --> 00:09:26,480
Yep Kevin O'Brien says the next comment didn't know about it.

120
00:09:26,480 --> 00:09:28,560
I never heard of any space museum.

121
00:09:28,560 --> 00:09:29,680
Where is it?

122
00:09:29,680 --> 00:09:35,120
And I get to the 22, 22, 22, 23 trip.

123
00:09:35,120 --> 00:09:38,320
You'll find that I hit a number of space-related sites.

124
00:09:39,040 --> 00:09:41,120
So yeah, I'll be cool to that one.

125
00:09:41,120 --> 00:09:42,320
This lots to come.

126
00:09:43,280 --> 00:09:44,480
That's an idea.

127
00:09:44,480 --> 00:09:44,640
Cool.

128
00:09:47,040 --> 00:09:48,480
Firefox extensions.

129
00:09:48,480 --> 00:09:51,040
And I walked through some of the

130
00:09:51,040 --> 00:09:53,520
Firefox extensions I have.

131
00:09:53,520 --> 00:09:57,280
And also, give a rundown of why I used them.

132
00:09:57,280 --> 00:09:58,320
There's one comment.

133
00:09:58,320 --> 00:09:59,840
Ron, can you read that?

134
00:09:59,840 --> 00:10:00,800
Sure.

135
00:10:00,800 --> 00:10:03,840
So we have a comment first comment by Joe.

136
00:10:04,480 --> 00:10:06,480
Plugins I've never heard of.

137
00:10:06,480 --> 00:10:07,600
Great episode.

138
00:10:07,600 --> 00:10:09,920
All of the mentioned extensions I have.

139
00:10:09,920 --> 00:10:12,720
Not heard of and look forward to testing them out.

140
00:10:12,720 --> 00:10:17,360
Appreciate you sharing some of the extensions you're using in a or have found.

141
00:10:17,360 --> 00:10:22,320
So the next day is UDM UBICODY setup for 2023

142
00:10:22,320 --> 00:10:22,960
operator.

143
00:10:24,240 --> 00:10:30,960
UBICODY setup on his system and provides us with a script which

144
00:10:31,040 --> 00:10:38,160
obviously has no, you should review before you download all missing

145
00:10:38,160 --> 00:10:38,800
sites.

146
00:10:38,800 --> 00:10:43,120
Are the UBICODY routers seem to be quite common in the states?

147
00:10:43,120 --> 00:10:47,200
I have never seen one in real life.

148
00:10:48,480 --> 00:10:49,680
Yeah, we end.

149
00:10:49,680 --> 00:10:50,480
Go on.

150
00:10:50,480 --> 00:10:54,480
So we have to say we actually have a couple of work.

151
00:10:54,880 --> 00:11:03,600
There's sort of gateway device and then like a managed switch and even like one of their

152
00:11:05,600 --> 00:11:08,160
the wire Wi-Fi access points.

153
00:11:08,160 --> 00:11:11,120
And they're nice, the work nice.

154
00:11:11,120 --> 00:11:15,440
And part of what I liked about them was they had like the local

155
00:11:15,440 --> 00:11:21,360
country, you know, their web interface controller that lets you, you know,

156
00:11:21,360 --> 00:11:23,920
you don't have to use it out in the cloud.

157
00:11:23,920 --> 00:11:25,760
You can have a local instance running.

158
00:11:25,760 --> 00:11:30,480
But the downside to that is it can be a little finicky to get running.

159
00:11:30,480 --> 00:11:36,880
And once you've sort of paired the device with a particular controller,

160
00:11:36,880 --> 00:11:41,040
it's kind of a pain if you need to move that controller or like you have a long

161
00:11:41,040 --> 00:11:43,920
non-forward a while and you can't remember which computer it's

162
00:11:43,920 --> 00:11:45,920
running on.

163
00:11:46,960 --> 00:11:51,840
It can be a bit tricky to, you know, you almost have to like make it

164
00:11:51,920 --> 00:11:55,760
refactory reset something to get it to go on to another controller.

165
00:11:55,760 --> 00:11:57,120
I mean, there's ways not to do that.

166
00:11:57,120 --> 00:12:00,960
But yeah, that's the only downside to them I've, I've found.

167
00:12:00,960 --> 00:12:03,920
But they're, they're okay, it's okay stuff.

168
00:12:05,200 --> 00:12:08,480
So the following day, we had creating a prompt for

169
00:12:08,480 --> 00:12:14,400
just GPT degenerate HBR's show is a rushed episode.

170
00:12:15,120 --> 00:12:19,840
People, even if you're submitting a show never say it's rushed episode.

171
00:12:20,800 --> 00:12:27,120
Where Mr. X creates a tap GPT prompt degenerate HBR episode.

172
00:12:27,120 --> 00:12:33,200
And I found this personally, more work, more work it went into this.

173
00:12:33,200 --> 00:12:35,760
That's what I've got into just doing the show.

174
00:12:35,760 --> 00:12:38,880
What, what do you guys think?

175
00:12:40,880 --> 00:12:43,280
Yeah, it's a great idea.

176
00:12:43,280 --> 00:12:48,160
I really liked the idea of doing this and it did seem like quite a lot of work

177
00:12:48,960 --> 00:12:55,440
to go backwards and forwards with chat GPT to get it to produce the correct instructions for

178
00:12:55,440 --> 00:13:02,320
itself to produce the show, which seems very, very torturous with to, yeah, I like the idea.

179
00:13:03,120 --> 00:13:08,080
Yeah, I'm still just coming to terms with learning, I mean, it's probably something I should

180
00:13:08,080 --> 00:13:12,560
like learn to play with because it does seem to be, you know, it's gaining momentum.

181
00:13:12,560 --> 00:13:16,000
I don't think it's going to go away, but I still have been this like,

182
00:13:16,000 --> 00:13:21,280
oh, I don't know if I want to deal with, yep, I'm the same right now.

183
00:13:21,280 --> 00:13:29,200
The same. In fact, I met up with Mr. X a couple of weeks ago now and we talked about this a little

184
00:13:29,200 --> 00:13:33,600
bit and it turned out that he's been using it a lot and I've used it once.

185
00:13:35,200 --> 00:13:41,680
So yeah, I don't know what it is that attracts certain people to it and repels people like

186
00:13:41,760 --> 00:13:47,280
me perhaps. That's a way of it. Well, people who seem to get an excited about it are the same

187
00:13:47,280 --> 00:13:55,360
people who get excited about Bitcoin, which is always a red flag in my book. I personally as a set

188
00:13:55,360 --> 00:14:00,320
people who can, is going to be a huge big thing and people are excited about your marketing,

189
00:14:00,320 --> 00:14:05,280
et cetera. Yeah, and I can see use cases for it, but at the end of the day,

190
00:14:05,280 --> 00:14:10,320
whatever this thing produces and if you're putting your name behind it, it's not,

191
00:14:10,320 --> 00:14:14,960
it that's going to be held responsible. It's you that's going to be held responsible. So, yeah,

192
00:14:15,840 --> 00:14:21,760
yeah, I mean, spell checking fine. If that's your thing, all to correct fine,

193
00:14:21,760 --> 00:14:25,760
if you want to produce a virtual chat GPT fine, the end of the day, professionally,

194
00:14:26,400 --> 00:14:32,160
you're putting your name behind that and that has not worked out very well so far for a lot of people.

195
00:14:32,160 --> 00:14:37,040
But we'll see what happens to be interesting for people in 20 years going back to listening to

196
00:14:37,040 --> 00:14:43,440
the show and going, oh, that was before the chat GPT became sentient and took over the world.

197
00:14:46,000 --> 00:14:53,040
Yeah, strengthening there was no comments about that, which is interesting.

198
00:14:54,000 --> 00:15:02,400
And the next day, we had episode seven hard to believe of the new years show for 2022, 2022,

199
00:15:03,360 --> 00:15:10,000
with as ever excellent shunnels by some guy in the internet on HP Lovecraft brilliant work.

200
00:15:10,000 --> 00:15:16,480
Okay, and it was nice. I mean, I, you know, just, I sort of spread through, I usually speed through these.

201
00:15:16,480 --> 00:15:20,880
I just, they're, they're not always my cup of tea, but it is nice, like they've been mentioned,

202
00:15:20,880 --> 00:15:25,200
like hearing, there were groups, you know, times when groups of people that sound like,

203
00:15:25,200 --> 00:15:29,680
they haven't been able to like get together or the shows that sort of brought them together,

204
00:15:29,680 --> 00:15:36,080
have moved on or they moved on, but they're getting to sort of have like a little mini reunion.

205
00:15:36,080 --> 00:15:40,240
Yeah, exactly. It was kind of weird, but there was a lot of people on the way,

206
00:15:40,240 --> 00:15:47,280
happened to the air cords spoken to in a while. And I happen, I'm, I'm a self-awesome on the,

207
00:15:47,280 --> 00:15:55,360
uh, episode that much. Um, so, uh, I missed out and to talk with a lot of people, so make

208
00:15:55,440 --> 00:16:01,920
more of an effort. There you go. I'm, I missed out completely, um, last year, or this year,

209
00:16:01,920 --> 00:16:08,640
whatever you call it. Um, yeah, so it's quite nice to, to hear. Um, just as an aside,

210
00:16:08,640 --> 00:16:14,880
can you break it up a bit? Yeah, as far as I, yeah, I'm hearing things. You're getting the same run.

211
00:16:15,680 --> 00:16:19,840
Yeah, there's been a couple times where you've broken up a little bit for a second or two.

212
00:16:20,800 --> 00:16:27,040
Mm, strange. Yeah. Don't know what that is. Okay. Just in case you could stop it.

213
00:16:27,680 --> 00:16:33,360
Yeah, I meant if, yeah, uh, yes. Well, just tell me if you know, since when the police

214
00:16:33,360 --> 00:16:39,920
wrote, okay, the following day we had SSH or open SSH escape sequences by Claudia Miranda.

215
00:16:40,640 --> 00:16:47,520
Wow, this was an excellent episode. I have never thought that you could do this

216
00:16:48,480 --> 00:16:54,960
within an ongoing session. Unbelievable. I had never heard of them. Let me perfectly honest.

217
00:16:54,960 --> 00:16:58,560
And then I finally this morning I was like, I don't know, let me see. And I was like, oh, wow,

218
00:16:58,560 --> 00:17:02,880
it does just pop up a little menu. And there they are. Just as you described.

219
00:17:03,920 --> 00:17:10,320
Yeah, I had to go and check it as well. Um, back in the day when we used Telnet, then you would, uh,

220
00:17:10,480 --> 00:17:18,640
there was escape sequences you could use to tell the Telnet client various things like

221
00:17:18,640 --> 00:17:23,520
clear the line or hang up or something. But, uh, yeah, I didn't know there was anything like that

222
00:17:23,520 --> 00:17:28,800
in SSH. It's actually quite quite potentially useful, I think. Uh, Retro, do you want to read the

223
00:17:28,800 --> 00:17:35,600
comment by Claudia himself? Yeah, sure. I hope I'm not breaking up this time. Um, Claudia

224
00:17:35,760 --> 00:17:43,840
I'm says, man SSH, the man will to add these sequences are also available in the man page for

225
00:17:43,840 --> 00:17:51,920
the SSH comment. Search for the title, escape characters in the man page. The man page, if you

226
00:17:51,920 --> 00:17:57,520
like to read it, um, well, I only if you understand it very well, it depends on the man page. I think

227
00:17:57,520 --> 00:18:04,400
quite a bit. There was a lot of both on the social internet about about this episode,

228
00:18:04,560 --> 00:18:09,520
particularly the BST people, a lot of people were commenting that they didn't realize that this

229
00:18:09,520 --> 00:18:16,640
was possible and life changing, et cetera, et cetera. Oh, cool. That mastered on you. We're looking

230
00:18:16,640 --> 00:18:23,200
out. That will be the master done. Yes. I didn't notice myself. There you go. Very good. It was

231
00:18:23,200 --> 00:18:31,360
really interesting because I mean, I would just quit the sessions usually or close it somehow and

232
00:18:31,360 --> 00:18:37,120
just go through it and I had no idea about this comments. Really valuable information.

233
00:18:37,120 --> 00:18:44,320
Exactly. Following day, we had plateau painting toy soldiers, uh,

234
00:18:44,320 --> 00:18:52,080
to start a painting miniature figures for war games, because hashtag is plateau. And, um, there was

235
00:18:52,080 --> 00:18:59,840
a comment by equal sign, but soldiers pointing to a YouTube. And really guys, we want me to think

236
00:18:59,920 --> 00:19:06,000
that that's some. This is exactly how you make a spam comment. But what it turns out to be

237
00:19:06,640 --> 00:19:13,920
is an excellent video. Can you hear me? Yeah, and I think you were breaking up on that.

238
00:19:13,920 --> 00:19:20,320
Yeah, reading that again. You know what I think it is, is my push to talk button not working. So,

239
00:19:21,200 --> 00:19:28,080
what it turns out to be is a piece of cushions video from a British paté. And if you don't know

240
00:19:28,160 --> 00:19:37,040
who he is famous English actor, very well known for being, um, uh, for the Star Wars, uh, general

241
00:19:37,040 --> 00:19:42,880
and Star Wars, the original ones. And hunting, hunting vampires at various points in this conversation.

242
00:19:42,880 --> 00:19:49,360
I think I remember him from the horror. Yeah. Thank you, sin Dracula. Was it even in a version of Dracula?

243
00:19:50,240 --> 00:19:57,840
So, definitely remember him knocking stakes into, uh, into some vampire or other. Yeah, he was, uh,

244
00:19:57,920 --> 00:20:04,400
part of that, um, hammer, uh, horror. Oh, yes, of course. Yes.

245
00:20:05,600 --> 00:20:12,240
Cool. People don't talk like that anymore. Hello, I was brought up in. Not very long after that

246
00:20:12,240 --> 00:20:19,760
era and did for a while. Yeah, he has said, I do my prep now, but it's great to hear. And

247
00:20:19,760 --> 00:20:25,920
apparently you enjoy playing soldiers, etc. Except for him. Now, sorry, I got just

248
00:20:25,920 --> 00:20:32,480
diverted there myself, reading the Wikipedia article. The following day, we had, yesterday I saw a

249
00:20:32,480 --> 00:20:38,000
solar flare on the counter the first time. Mike now that you saw a solar flare with his own eyes.

250
00:20:38,000 --> 00:20:44,000
And now he is legally blind. No, he didn't watch it with his own eyes. He watched it through

251
00:20:44,560 --> 00:20:50,640
the proper equipment thus sparing his eyes. Yeah, really, uh, found this, uh, I really found this

252
00:20:50,720 --> 00:20:56,640
an interesting episode. It's, it's pretty cool to just think you couldn't sort of see them.

253
00:20:56,640 --> 00:21:00,240
Like, I mean, I know you, you know, there's ways to detect them. I just didn't, I just hadn't

254
00:21:00,240 --> 00:21:05,280
really thought about the fact that you could, you know, properly protected, look at it, you know,

255
00:21:05,280 --> 00:21:12,880
with your own eyes. Yes. And, and the fact that very few astronomy people actually do that was also

256
00:21:12,880 --> 00:21:18,160
quite interesting. Looking at his show notes, I especially liked picture at the bottom where the

257
00:21:18,240 --> 00:21:27,600
sun is well-looking, very special. Yeah. Yeah, it looks like a pizza sort of melting or something.

258
00:21:27,600 --> 00:21:35,760
Yeah, it doesn't. Yeah, nice. Nice idea. So the next day we had a new news, some guy in the internet

259
00:21:35,760 --> 00:21:43,360
talks about the Toyota's data leak and more in the all-know news. And Kevin O'Brien says, this is a great

260
00:21:43,360 --> 00:21:49,840
series. I do love the all-know news. Please keep it up. More about that leisure. And the following

261
00:21:49,840 --> 00:21:59,840
day, we had GWP, uh, with my life, my life in devices, where he talks about various devices

262
00:21:59,840 --> 00:22:06,800
and my purchase and there's no content, but it was, it could be show, I don't know. I am

263
00:22:06,800 --> 00:22:13,600
not seeing the transcript for this, David. Oh, cause was that the one that I missed? I don't remember

264
00:22:13,600 --> 00:22:20,000
to be honest with you. I've done a new laptop during this period and, uh, they, uh,

265
00:22:20,000 --> 00:22:25,600
on all I upgraded Fedora and it broke whisper, which is the tool we used to do the transcripts.

266
00:22:25,600 --> 00:22:32,080
So perhaps that's it. Any comments on this episode or shall I move on? So I was just making a note

267
00:22:32,080 --> 00:22:38,000
of that, uh, show to go and look at it. See what went wrong. Yeah, it's, it's good. He's got

268
00:22:38,880 --> 00:22:43,600
GWP has all sorts of weird and wonderful machines. It's always good to hear about that. I think

269
00:22:43,600 --> 00:22:50,160
I think he meant it to say my living devices. Do you think? Yeah, good thing when the things he's

270
00:22:50,160 --> 00:23:00,240
lived with. Yeah. Okay. Yeah. So civilisation, too. This was a show by Huka about the strategy

271
00:23:00,320 --> 00:23:06,160
game, civilisation. And to be honest, I don't play computer games or games in general.

272
00:23:07,040 --> 00:23:15,520
And both fist, fist was quite cool to follow along with this. So yeah, nice. Yeah, Huka,

273
00:23:15,520 --> 00:23:22,880
Huka mentioned something that I thought about it. He said back in the days, he could look at

274
00:23:22,880 --> 00:23:27,360
the clock and it was for a clock in the morning or something like that. And this is one of the

275
00:23:27,360 --> 00:23:35,840
reason why I wouldn't play or even start with such a strategy games. Yeah, good point. Yeah, exactly.

276
00:23:36,560 --> 00:23:42,560
So the next thing is how to find things at your home network, how to find a lost Raspberry Pi

277
00:23:43,520 --> 00:23:52,160
zero on your home network. Again, by JWP, it's an app called network analyzer on his Huawei phone.

278
00:23:52,720 --> 00:23:59,040
It would never come into my mind to search it via the mobile phone. I thought it was quite special

279
00:23:59,040 --> 00:24:06,240
on his approach. My go-to would be an arc, look up, ping everything and then do an arc, look

280
00:24:06,240 --> 00:24:12,400
up from. I would go to my router and see what is connected. True, true, that's not what you're doing.

281
00:24:12,400 --> 00:24:17,680
I think I used to like using, would it be net count or something, or you can, yeah, you can

282
00:24:17,760 --> 00:24:27,440
quiz that for all devices it can, it can see, which is, yeah, but yeah, it's just because I've got an

283
00:24:27,440 --> 00:24:33,840
alias to it, my heartly of the users who I can't remember. I was doing a show previously on

284
00:24:33,840 --> 00:24:40,320
locating Raspberry Pi's on your network. And while the easiest thing is to go into your router

285
00:24:40,320 --> 00:24:47,120
on a podcast, it's difficult because every router is going to be different. So doing the ping

286
00:24:47,120 --> 00:24:53,520
look up kind of makes more sense because it's generic and not anybody can do it. It's in map

287
00:24:53,520 --> 00:25:00,320
that I couldn't remember there. And in map, yes, on on the whole subnet is what I got configured

288
00:25:00,320 --> 00:25:08,640
in my alias. So the following day, Archer 72 did a response episode to my episode and goes over

289
00:25:09,600 --> 00:25:15,360
a lot of plugins. And one I particularly dislike is the I don't care about cookies,

290
00:25:15,360 --> 00:25:22,400
cause for the rest. You should very much care about cookies and turn them off manually.

291
00:25:22,400 --> 00:25:29,520
It sends a message back to the website's not to track you. One of you guys mentioned that I still

292
00:25:29,520 --> 00:25:36,160
don't care about cookies, which sounds almost similar, but because of us, the virus,

293
00:25:36,160 --> 00:25:43,040
Antivirus, Manufacturer, which had some bad reputation in the past that took over that

294
00:25:43,760 --> 00:25:54,000
dead software. Interesting. I don't like this the one I had to be. I know people love dark mode

295
00:25:54,000 --> 00:26:00,880
and I like it for some things, but I don't know if it's what it is, but I like my light mode.

296
00:26:01,760 --> 00:26:06,400
Yeah, so I'm struggling with dark mode. I've got dark mode and a fair number of things,

297
00:26:06,400 --> 00:26:12,640
but I find that terminals with it and then you start up them and the contrast between the

298
00:26:12,640 --> 00:26:19,760
different syntax colors and stuff is too, I just can't read them sometimes. I've got to be really

299
00:26:19,760 --> 00:26:28,800
careful about that. It's an aged thing or an I thing. I'm not sure I would go for dark mode and

300
00:26:28,880 --> 00:26:33,040
everything that's basically what I'm saying. I was trying not to mention the age thing too.

301
00:26:34,800 --> 00:26:44,400
I've thought about myself. Yes. It's a days as me how fashions go so quickly through IT,

302
00:26:44,400 --> 00:26:48,960
you know, everybody all of a sudden, all of the applications have to have a dark mode.

303
00:26:48,960 --> 00:26:55,840
Yes, and invisible scrollie bars for some reason has become

304
00:26:56,800 --> 00:27:03,280
I think. And yes, if you want people to change so you can change the format of the days function

305
00:27:03,280 --> 00:27:08,560
in your application. No, no, no, we can't do that. That's what we can do, but we can spend all this

306
00:27:08,560 --> 00:27:15,520
time changing dark modes and messing around with you guys. It's just amazing.

307
00:27:16,640 --> 00:27:25,200
Yeah, yeah. I spend lots of my time struggling with these things. Being a KDE user, I'm constantly

308
00:27:25,920 --> 00:27:32,400
tweaking stuff. Why is this, why is this window not got a title by others different color from

309
00:27:32,400 --> 00:27:37,200
the rest of it? Because when they're overlay, they're really hard to see. So I just been trying to

310
00:27:37,200 --> 00:27:42,720
make sure I've got that enable properly those sorts of things. Not saying that there shouldn't be

311
00:27:42,720 --> 00:27:47,760
dark modes. I'm just saying it amazes me how popular all of a sudden it wasn't popular and then

312
00:27:47,760 --> 00:27:54,960
everybody has it on everything. Even in work like wiki pages and work suddenly. Although we've

313
00:27:55,280 --> 00:28:00,160
got a dark mode, don't want it. Thank you. I'm gonna say goodbye. Just the other day,

314
00:28:00,160 --> 00:28:07,680
I followed up on on your add-ons for for the copy stuff and you used the rations changes.

315
00:28:08,400 --> 00:28:14,960
And what was interesting to me on the one from now, I don't have to name, from Marcher 72,

316
00:28:14,960 --> 00:28:23,680
is I use something for YouTube already, but the extensions or the add-ons, he mentions for YouTube,

317
00:28:23,680 --> 00:28:29,680
or quite interesting. I wasn't aware about those that you could even mention when some

318
00:28:29,680 --> 00:28:35,200
advertisement is inside that is spoken where they can share it. This was a really interesting

319
00:28:36,480 --> 00:28:45,920
idea from the one who developed it. Yeah, I didn't follow that one up yet, but it sounded amazing.

320
00:28:46,640 --> 00:28:54,560
It could use for AI. I'm speaking of AI. The episode we spoke about previously

321
00:28:54,560 --> 00:29:01,360
about Mr. X and ChatGPD. This is the article that HPR that he produced using that.

322
00:29:02,000 --> 00:29:08,800
So that was also interesting, actually. Yeah, I actually enjoyed listening. I mean it was, it was

323
00:29:09,360 --> 00:29:18,480
I thought it was a pretty good episode. Yeah, and I enjoyed this one. Yeah, I think I seemed to have

324
00:29:18,480 --> 00:29:24,080
spent most of my time puzzled over how an earthy managed to get it to do what he did right

325
00:29:24,080 --> 00:29:31,600
and listened to the content. Now I come to see it's quite a large set of show notes here, but very,

326
00:29:31,600 --> 00:29:37,920
very good. So the following day we had the New Year show part 8 and there were no comments about that.

327
00:29:39,440 --> 00:29:47,280
And the day after that, we had when did the internet get so boring? So some thoughts about

328
00:29:47,280 --> 00:29:55,440
the modern web as part of the information on the ground. And it's about, yeah,

329
00:29:56,320 --> 00:30:04,160
chat to talks about the stages of the web. And Hammer on has a good comment there.

330
00:30:04,160 --> 00:30:08,480
So do you want to volunteer to read it or shall I? I can read it. Go first.

331
00:30:08,480 --> 00:30:16,640
I grab coffee at the meat house. From Hammer on, why did the internet get so boring?

332
00:30:16,640 --> 00:30:22,000
Glad to. I found this episode to be very relatable to me. I missed the vast quantities of those

333
00:30:22,000 --> 00:30:27,760
independent websites such as geosities that you mentioned. I almost forgot about how poor,

334
00:30:28,080 --> 00:30:35,920
how poor coded they were. I'd sometimes see text ever written with graphics on top or other text.

335
00:30:35,920 --> 00:30:40,720
It's hard for me to complain on that issue as my own personal website might not be written much

336
00:30:40,720 --> 00:30:46,240
better, but it's mine and I'm learning as I go along. There's small sites, though, far less common

337
00:30:46,240 --> 00:30:52,960
than days gone by, had a vibe that is far from the mostly corporate base sites today.

338
00:30:52,960 --> 00:30:56,800
It was nice when you'd see a description of what people were doing from their point of view.

339
00:30:57,520 --> 00:31:03,200
A recipe from a grandmother, a hike along a favorite trail, a little known, but much

340
00:31:03,200 --> 00:31:10,640
loved music group, games, stories, poems. Many graced with gifts such as dancing flames on a torch,

341
00:31:10,640 --> 00:31:16,880
dancing animals, or fantasy castles and dragons perhaps copied from elsewhere. Many had background

342
00:31:16,880 --> 00:31:23,440
music from MIDI files with their electronic tones. As you stated about modern sites,

343
00:31:23,520 --> 00:31:29,680
tended to talk and not listen a lot. I totally agree. A problem that I encounter is when doing a

344
00:31:29,680 --> 00:31:36,080
web search looking for information, the sites often are not a good match for my search terms and more.

345
00:31:36,080 --> 00:31:41,040
Few of the sites offer quality information, most instead being geared for sales,

346
00:31:41,040 --> 00:31:47,360
hear them talk. It's like entering a library to find that it is not a library but a department store.

347
00:31:48,160 --> 00:31:53,280
Something I've recently noticed is that if I look for a particular website, say, let's say,

348
00:31:53,280 --> 00:32:00,000
comparing Linux districts, I can go several websites and a few of the sites will have identical

349
00:32:00,000 --> 00:32:06,000
descriptions, word for word. It's a shame to visit site after site to find information not similar,

350
00:32:06,000 --> 00:32:12,640
but a bad identical. Well, thank you for good the podcast, glad to and thanks to HPR, hammer on.

351
00:32:12,720 --> 00:32:18,800
For the hammer on. The thing he missed was the under construction

352
00:32:19,600 --> 00:32:27,760
icons gifts. Remember the eye? Yeah, they were nice. Regardless of what stage your website was,

353
00:32:27,760 --> 00:32:32,880
it had the under construction and the gift on it. As one of you ever given the goal to

354
00:32:32,880 --> 00:32:42,640
disqual for? I have worked to the university where we implemented it. In fact, I implemented it

355
00:32:42,640 --> 00:32:49,520
for as a sort of campus-based information system and it was on the internet but it was really

356
00:32:49,520 --> 00:32:54,880
for the campus rather than anything else. Yeah, it was, it was good but we were happy to move away from

357
00:32:55,040 --> 00:33:04,160
it once web browsers and web service started to rise. I never was on this server side and I

358
00:33:04,160 --> 00:33:09,440
think really the first time I used to go for was like in a web browser because I think like the

359
00:33:09,440 --> 00:33:18,400
early like net scape and whichever previous ones like the that mostly have, yeah, that's it,

360
00:33:18,400 --> 00:33:26,240
as they had they built go for in to it. So you could and FTP and all the good fun stuff. So you

361
00:33:26,240 --> 00:33:34,800
could it was sort of a multipurpose tool back then. There's been an effort to do something along

362
00:33:34,800 --> 00:33:44,240
the lines of go for a protocol called Gemini which I've been considering now once we're on the

363
00:33:44,320 --> 00:33:48,480
static site that we can also generate Gemini pages and it shouldn't be too difficult.

364
00:33:50,000 --> 00:33:57,680
But yeah, if you want to see some old school into their pages just look up some hand-read

365
00:33:57,680 --> 00:34:04,240
your stuff and you're immediately go back to websites designed in 1990. Still been maintained but

366
00:34:04,960 --> 00:34:09,440
they look and feel are still there, you know, yep, there's a hand-read your website.

367
00:34:10,080 --> 00:34:17,760
But that was a good show. That show had been thinking actually, I've been thinking a lot. Introducing

368
00:34:17,760 --> 00:34:28,000
myself. This is by Roni Kuhi. Andre Yanish. Yeah, that'll do.

369
00:34:28,800 --> 00:34:36,320
Also, at least his name is the Rayunoki is, yeah, I would say Rayunoki. He does actually say it

370
00:34:36,320 --> 00:34:42,800
in the show, but I forgot to go back and listen and learn it from there. But my next time we'll know.

371
00:34:43,520 --> 00:34:51,440
You know, for every host, I have a wildfile where they introduce themselves and I save that.

372
00:34:51,440 --> 00:34:56,000
That was something else for the static site in the direct, in the host directly, you know,

373
00:34:57,280 --> 00:35:01,760
horse name or something like that. That would be nice. Yes, well, good idea.

374
00:35:02,480 --> 00:35:08,960
What I thought was funny with him is, I had once a mouse when you especially a lot

375
00:35:08,960 --> 00:35:14,320
you take, I think, is when you click the button, you get this double hammering. It's like when

376
00:35:14,320 --> 00:35:19,760
when it's getting old and all you would have to do is clean the context a little bit. So the mouse

377
00:35:19,760 --> 00:35:24,160
is basically broken because it drives you mad when it does a double click if you don't want to.

378
00:35:24,160 --> 00:35:29,840
And now he says, he has broken computers, so to say your computers, he no longer needs.

379
00:35:30,160 --> 00:35:37,040
So, so what does I am hinted you to take those things apart if you were, don't use it anyway,

380
00:35:37,040 --> 00:35:42,000
why not just go for it and learn? You've already broken, I can't be more broken.

381
00:35:42,000 --> 00:35:48,880
Right, isn't it? There was so much in this episode. I totally agree with you by the way, Rata.

382
00:35:48,880 --> 00:35:56,160
There was so much in the episode, I'm looking at FirefoxOS, there's a show, F-trudge,

383
00:35:56,160 --> 00:36:04,240
there's a show, old stuff and fairfong, there's a show's. I could talk about mathematics.

384
00:36:04,240 --> 00:36:10,560
Well, now as it so happens, we have a mathematics series here in HPR Plus. I have

385
00:36:11,440 --> 00:36:17,840
some mathematical stuff that I need for the H, for the hand radio exam course,

386
00:36:18,640 --> 00:36:23,520
that I would appreciate people's help from the mathematics community to explain that stuff.

387
00:36:24,480 --> 00:36:27,200
So, get in touch with me about that, please.

388
00:36:27,200 --> 00:36:35,360
Let me see any other shows. Think about, yes, reviews, breakdowns, upgrades, hate to people in laptops,

389
00:36:35,360 --> 00:36:39,920
farad, all machines from the dossier. We have a dossier here in HPR.

390
00:36:41,120 --> 00:36:43,680
So, I'm expecting big things here.

391
00:36:45,200 --> 00:36:46,560
Welcome to the fold.

392
00:36:46,560 --> 00:36:47,520
Exactly.

393
00:36:47,520 --> 00:36:54,880
Who's got to do art here? I've done one for a while, I can do art here 72.

394
00:36:55,440 --> 00:37:01,600
Who says show ideas. First of all, welcome to hear. It was a good introductory show.

395
00:37:02,080 --> 00:37:06,720
You mentioned four topics that would be interesting to a lot of listeners.

396
00:37:07,840 --> 00:37:15,840
Web development and coding, mathematics, music theory, electronics pertaining to computer repair.

397
00:37:16,000 --> 00:37:23,760
On music theory, I would also like to hear more. As a child of 12 years, I did play the piano,

398
00:37:23,760 --> 00:37:28,560
but didn't go far with it. Without I can still play a few notes.

399
00:37:28,560 --> 00:37:31,920
With electronics, less of my experiences in computer repair,

400
00:37:31,920 --> 00:37:37,120
or this is preparing electronics in a factory setting, although knowledge here is not what it could be.

401
00:37:37,120 --> 00:37:41,840
Maybe not you, but another host might like to do one or an Arduino. Again,

402
00:37:41,920 --> 00:37:45,920
limited experience here, but this would be an interesting avenue to explore.

403
00:37:46,480 --> 00:37:52,800
Just 72. I think we need to put art to 72 and some guy on the internet into our

404
00:37:54,000 --> 00:38:00,320
host, host, something team. What will we call those? A publicity department.

405
00:38:01,280 --> 00:38:05,840
I second that move. Absolutely. Yes, yes. I would try to think what the word would be

406
00:38:05,840 --> 00:38:10,880
back out. Yeah, especially in the whole context of the genre of the process.

407
00:38:10,880 --> 00:38:14,480
Customer relations. Absolutely. There's some horror like that.

408
00:38:14,480 --> 00:38:15,760
There's a little perception of, yes.

409
00:38:19,120 --> 00:38:25,120
All in day, genuinely it was our role, and did installing leap 15.1.

410
00:38:25,120 --> 00:38:28,480
I think that's the role in release of Open Susan.

411
00:38:29,280 --> 00:38:34,720
On a fugitive, as in 1910, it's very, very interesting.

412
00:38:35,600 --> 00:38:40,000
Would not thought to run Docker on that, but why not, actually?

413
00:38:40,000 --> 00:38:44,560
Yeah, as I said before, JWP has some weird and wonderful equipment.

414
00:38:45,600 --> 00:38:52,960
He has mentioned this device before, but yeah, I think I've probably seen one in my,

415
00:38:53,600 --> 00:39:01,200
certainly had a bunch of these in my work in the earlier days, but I wouldn't

416
00:39:01,200 --> 00:39:07,360
consider every using these days. Good for him. Yeah, cool. Excellent. Excellent.

417
00:39:08,960 --> 00:39:11,120
Are we haching the end today?

418
00:39:13,360 --> 00:39:20,720
3868 is the last one. 3868 is the news reports and recent, as some guy in the internet again,

419
00:39:20,800 --> 00:39:26,160
reports and recent FBI criminal reports and other news. If you like it, help me the image.

420
00:39:26,160 --> 00:39:33,520
So that was that, and there was one comment. JWP says the news show.

421
00:39:33,520 --> 00:39:40,400
Hi, I really like the news show. Easy to follow. Good. I didn't like it so much. I

422
00:39:40,400 --> 00:39:50,000
thought it wasn't in opposite to the security. Oh, no news. He did before. This was, well,

423
00:39:50,000 --> 00:39:56,480
I don't know, maybe it was just be, but it felt quite negative somehow. I don't know how to express that.

424
00:39:56,480 --> 00:40:04,320
Okay. Well, yeah, I suppose it's difficult to to pick and use, yeah, it's difficult to pick

425
00:40:04,320 --> 00:40:12,880
and use in general, hopping use as well, might be hard to find. I think that was the sort of

426
00:40:12,880 --> 00:40:21,520
the sentiment for me, too. I guess I have enough sort of news, news feeds in my feed reader,

427
00:40:21,520 --> 00:40:28,160
that for me, this was like, I sort of come to a hacker public radio, not to sort of hit the sort

428
00:40:28,160 --> 00:40:36,000
of more general news in a way. I mean, he does it well. I do, and I appreciate how much God

429
00:40:36,000 --> 00:40:43,760
he's really putting it effort into, well, everything he does, obviously, but just improving his podcasting

430
00:40:43,760 --> 00:40:48,320
and then providing, you know, really dedicated to the community, but this for me just doesn't

431
00:40:48,960 --> 00:40:54,880
quite hit it yet. Now, maybe it's just one episode and he hasn't found the stride yet for it.

432
00:40:55,680 --> 00:41:02,240
But I definitely lean more towards the owner news and it's current format than sort of like this

433
00:41:02,640 --> 00:41:10,080
companion news. Yeah, I tend to agree actually on reflection. I just hadn't quite

434
00:41:11,120 --> 00:41:16,720
been as discerning as you guys were with it. I just thought, oh yeah, a bunch of news,

435
00:41:16,720 --> 00:41:22,960
interesting. Thanks for presenting it. But yeah, looking at it now, I think you're right.

436
00:41:23,440 --> 00:41:33,280
Maybe I'm not sure quite what the intention is. So something a little bit more

437
00:41:33,280 --> 00:41:39,360
to make sure, perhaps, might be better. I don't know. Quality wise, I'm totally impressed by his work,

438
00:41:39,360 --> 00:41:45,440
how he does the different voices or this auto, I don't know what it is, but I'm totally impressed,

439
00:41:45,440 --> 00:41:52,560
how he does it and how much time he really is spending his was just the content of it,

440
00:41:52,560 --> 00:42:02,480
didn't fit my, as Ryan already said before. Mm-hmm. Okay, I think that's the end of the

441
00:42:02,480 --> 00:42:08,720
shows, but it was one comment. I think it was left by you, Retro. Would you like to read that out?

442
00:42:09,680 --> 00:42:16,560
It's on the page itself, all of a sudden you're linking the mobile shots. Okay, it's opening.

443
00:42:17,520 --> 00:42:22,720
Um, I did a big red one that Dave tells us never to mention a big red line round.

444
00:42:23,600 --> 00:42:28,560
Oh, okay. Okay. Um, oh, this is one that I left for Macatroniac.

445
00:42:29,280 --> 00:42:37,680
Hi, Macatroniac. Um, having a coup, having Ocus, Ocus on hand, with different voltage sounds good.

446
00:42:38,400 --> 00:42:46,240
Almost like Ken, I don't think soldering destroys the Ocus as long as you have a large soldering

447
00:42:46,240 --> 00:42:54,480
iron. By the way, large means it can keep a lot of heat, so you can really quickly heat something up.

448
00:42:55,200 --> 00:43:01,040
There's a lot of things. Exactly. It goes further. Why not building a do your own spot

449
00:43:01,040 --> 00:43:09,920
welding machine? I watched some videos in the past, like then I put in a link from a YouTube video

450
00:43:10,000 --> 00:43:18,720
how they took from an old microwave, the transformer, I think you say, and or a bit more risky.

451
00:43:18,720 --> 00:43:24,640
You can just take a small car battery, maybe a motorbike, battery will do it as well,

452
00:43:25,040 --> 00:43:31,440
and just use that one. But the battery has no switch. Um, so you should have to be careful.

453
00:43:31,440 --> 00:43:36,960
You seem making a traffic stop. You shouldn't be giving the guy more dangerous stuff to be doing.

454
00:43:36,960 --> 00:43:49,200
We're trying to get him working safer, not more dangerous. Oh, there was, uh, two comments on

455
00:43:49,200 --> 00:43:56,240
previous shows. Um, the D1 mini closed scan to lead by me, and the comment was by me. I need to put

456
00:43:56,240 --> 00:44:02,880
this on Perf board, uh, thanks Dave for having the schematic on RAPI.org for me to find

457
00:44:02,960 --> 00:44:09,760
based on the bash finally. This is how my life works now. Since then, I have one perf board

458
00:44:09,760 --> 00:44:15,200
and found out that my perf board is cheap and crappy. So I need to get more perf board.

459
00:44:16,480 --> 00:44:26,080
And Roland, do you want to do archa 72's last comment, and then we can move on. So, um, on for episode

460
00:44:26,720 --> 00:44:33,840
353H installing the tenacity audio editor by archer editor, archer 72, we have a comment

461
00:44:33,840 --> 00:44:41,680
by archer 72, uh, my memory. These shows are my memory, not only my shares, but a multitude of

462
00:44:41,680 --> 00:44:47,840
other shows. I have recently had to reference this one. I had hoped that tenacity would be in the

463
00:44:47,840 --> 00:44:53,600
fedora 38 repos, but no. Still, tenacity is alive and well, and is currently has implemented a

464
00:44:53,680 --> 00:45:00,560
darkening, which I definitely did not. I'll say newly integrated are the clip handles to move around

465
00:45:00,560 --> 00:45:08,960
audio clips instead of a separate tool. Okay, sorry, so one of the four of us at this day

466
00:45:08,960 --> 00:45:15,280
alive as it sounds. Yeah, yeah, I haven't used tenacity, I've read about it, but

467
00:45:16,400 --> 00:45:22,160
apparently it is still alive and kicking. I was looking to see if it was alive just the other

468
00:45:23,040 --> 00:45:30,320
had a conversation with Mr. X on that subject, and to me it looked like it was dying, because

469
00:45:30,320 --> 00:45:37,680
there's not been, there would be many releases in quite a long time, but I might have misunderstood

470
00:45:37,680 --> 00:45:42,640
what I was reading there, I don't know. If somebody has more information on that, they can always

471
00:45:42,640 --> 00:45:48,640
record a show, the idea that would be good to know, actually. Yeah. Okay, a lot of movement

472
00:45:48,720 --> 00:45:59,440
there on the old milling. One of the first ones was by Operation, and it was about, I won't read

473
00:45:59,440 --> 00:46:06,320
it, because it was about an ericode related to posting show with comments, and we have,

474
00:46:08,400 --> 00:46:15,680
okay, we have this thing where a comments, if you're posting on comments for the last two weeks,

475
00:46:15,760 --> 00:46:20,880
that it only shows three questions, and if you're posting on the future feed or on the

476
00:46:20,880 --> 00:46:26,160
past feed, then there are more questions, and they require a huge fill in additional stuff.

477
00:46:27,200 --> 00:46:32,160
That will be coming standard for a while for reasons which we're going to later.

478
00:46:32,960 --> 00:46:42,000
And Ron, yeah, okay, I'll quickly go through these. Ron said in a message about the

479
00:46:42,000 --> 00:46:49,680
Getty instance migrating to the new server. The IP address is there. So if you run into issues

480
00:46:51,200 --> 00:46:58,720
with your key being giving errors, that's the reason for that. And then policy. So first of all,

481
00:46:59,440 --> 00:47:05,040
by me, first of all, we need more shows as the Q is empty for the next number of weeks.

482
00:47:05,440 --> 00:47:12,880
The number of emergency reserves are also doing, so please finish the shows that you were thinking

483
00:47:12,880 --> 00:47:18,480
of submitting and sending it in. If you don't care, when it's released, put in use as emergency

484
00:47:18,480 --> 00:47:25,920
show in the show notes for now. And that is also still relevant today as we speak. So we're just

485
00:47:25,920 --> 00:47:32,240
keeping the Q sort of filled all the time, and we need more people to contribute. Yes, thank you very

486
00:47:33,200 --> 00:47:38,240
much. Then I'll continue on. I'm concerned about the future of HBO as a project where the

487
00:47:38,240 --> 00:47:44,080
shows are produced by the community. At this rate, we cease to be a bar camp style podcast and

488
00:47:44,080 --> 00:47:52,160
become one where the shows are provided by a rotating team of regulars. Ideally, we would like to

489
00:47:52,160 --> 00:47:57,760
have every show is contributed by a different host, giving a one to one risk here between

490
00:47:57,760 --> 00:48:05,760
show and host. As far, so far, we see here all the four of the submissions are from

491
00:48:05,760 --> 00:48:13,520
hosts who submitted more than one show. So this is a three to one ratio. A hook aside, the majority

492
00:48:13,520 --> 00:48:20,080
of the results of kind-hearted hosts who contribute shows at the last minute to fill a vacant

493
00:48:20,080 --> 00:48:26,720
slot in the Q. This problem, to make this problem more visible, I would like to introduce the

494
00:48:26,800 --> 00:48:34,240
following scheduling guidelines. No host should submit any more than one show in a two week period.

495
00:48:34,240 --> 00:48:39,200
Of course, these are guidelines, et cetera, but it should still allow for a little if it

496
00:48:39,200 --> 00:48:44,480
calls to the submissions who are now masking the underlying issue that we have yet to address,

497
00:48:44,480 --> 00:48:50,480
which is, we need new hosts, but we also need old hosts who have not submitted shows this year

498
00:48:50,480 --> 00:48:56,000
to submit a show. How do we solve this problem? And I realize reading that that is terribly

499
00:48:56,080 --> 00:49:04,160
worded, but I don't know, we will go on and somebody read the next message you did. Can you read

500
00:49:04,160 --> 00:49:13,680
Nigel's response? Yep, yep. So this is Nigel Verity who says hi can. I'm one of the many occasional

501
00:49:13,680 --> 00:49:20,480
contributors who's always and genuinely just about to put a show together. Slapped risk accepted,

502
00:49:20,560 --> 00:49:26,560
we'll do better. We are very fortunate that the prolific hosts generally put out such excellent

503
00:49:26,560 --> 00:49:32,640
well presented shows. Could there perhaps be some mileage in contacting all the top Linux and

504
00:49:32,640 --> 00:49:39,440
more general IT podcasts to put out an invitation for their listeners or even host themselves to contribute?

505
00:49:39,440 --> 00:49:44,080
There are some extremely knowledgeable people amongst those presenters, so it's probably

506
00:49:44,080 --> 00:49:51,200
safe to assume this will be reflected to some extent in their audiences. And this is Beezer,

507
00:49:51,200 --> 00:50:00,560
it's his handle. Excellent idea. And if there are people who can do that for us and go get

508
00:50:00,560 --> 00:50:06,400
interviewed on those shows and explain about HPR is and stuff, if you're actively involved in

509
00:50:06,400 --> 00:50:12,560
another podcasting community, can you please take that upon yourself to do it? Don't just wait

510
00:50:12,560 --> 00:50:21,040
for somebody from HPR, one of the genesis to do it. You're listening to HPR, if you need

511
00:50:23,200 --> 00:50:28,160
some information about what HPR is and stuff, we can supply that to you, but feel free to

512
00:50:28,160 --> 00:50:34,240
get in contact with these people. And if you're most put admin at Hacker Public Radio on the CC,

513
00:50:34,320 --> 00:50:43,680
excellent, excellent. Next one, can you read that retro, Magnale, please?

514
00:50:45,200 --> 00:50:52,160
Andrew Conway, I can at all, I have a show that just needs an edit, so I will do that now.

515
00:50:52,800 --> 00:50:58,000
I really understood from somewhere that more than one show per fortnight was thrown up on.

516
00:50:58,880 --> 00:51:02,800
Don't recall from very exactly, so that guideline is fine by me.

517
00:51:03,600 --> 00:51:10,080
One suggestion for increasing diversity invites someone you know to do a show with you.

518
00:51:10,800 --> 00:51:16,640
I'm sure we all know folk who have interesting things to say, but we're not yet on HPR.

519
00:51:17,440 --> 00:51:24,000
We can then point out the guest how easy it is to record and submit the show. Smiley.

520
00:51:24,720 --> 00:51:31,280
Also, we can spice things up a bit by doing shows with a co-host from among our own ranks.

521
00:51:32,000 --> 00:51:40,960
If there are n hosts, there are many more than n co-hosting pairs. In fact, it is n choose to,

522
00:51:41,680 --> 00:51:48,240
which can be expressed mathematically as I will do a show in greater than two weeks times.

523
00:51:48,960 --> 00:51:56,080
Andrew, Magnale is his abbreviation, I guess, in the HPR.

524
00:51:57,600 --> 00:52:03,600
I think it is interesting, for me, as I live in Switzerland, I don't have so many people who would go ahead

525
00:52:03,600 --> 00:52:11,840
and say, let's do a chat in English. Maybe more appropriate for one of the new persons

526
00:52:11,840 --> 00:52:20,960
that for the hosts in the UK or the US, or it's easier to find someone than on the other hand,

527
00:52:20,960 --> 00:52:27,520
where can these hosts find each other from this community when he says to find the co-hosts

528
00:52:27,520 --> 00:52:31,040
who is already doing something on HPR. Where is the best place for that?

529
00:52:31,040 --> 00:52:37,920
Well, I can think of two people straight off who we are Benny, who lives in Switzerland.

530
00:52:38,560 --> 00:52:45,520
And we also have, although it's never done a show actually, on together with you, he did that.

531
00:52:46,240 --> 00:52:54,720
Nope, I need it. That's correct here. From the podcast, what's his name? French guy from

532
00:52:54,720 --> 00:52:58,000
French speaking guy from Switzerland. So, Yannick. Yannick, Yannick, Yannick, Yannick, Yannick, Yannick.

533
00:52:58,960 --> 00:53:03,280
So, you may have Yannick and tell him to do a show. That will be excellent.

534
00:53:03,920 --> 00:53:09,920
Okay, you catch me. Can you do tattoos one please?

535
00:53:12,640 --> 00:53:19,760
Rolled. Okay, from Clotoo, I agree with Minix. Fewer rules make for easier

536
00:53:19,760 --> 00:53:26,080
compliance for the content creator. If we want to maximize incoming content, we should take

537
00:53:26,080 --> 00:53:32,720
what we can when we can, whenever the content provider wants. It means we have a week of just one

538
00:53:32,720 --> 00:53:39,440
host on a recording spree. That's okay. People control their own playlist. They can mix it up as they

539
00:53:39,440 --> 00:53:46,000
prefer. If we want to reserve the right move episodes around as we see fit, then let's stop

540
00:53:46,000 --> 00:53:50,560
asking people to reserve episode numbers and just say that the content gets scheduled as

541
00:53:50,560 --> 00:53:56,080
the schedule sees fit. We get to make the rules. If people don't like how we

542
00:53:56,080 --> 00:54:01,360
operate, then they don't have to submit shows. There are lots of places to post stuff on the internet.

543
00:54:01,520 --> 00:54:05,760
We're just one place. Let's make it easy for people to create content for HDR.

544
00:54:05,760 --> 00:54:12,320
And easy for HDR to publish daily, which is it's data goal. We skipped over the one that

545
00:54:12,880 --> 00:54:18,960
Minix has said, if the survival of HDR does pen solely on new hosts, then you might as well

546
00:54:18,960 --> 00:54:24,720
fold the show. If the survival of the show depends on getting show period with a smattering of new

547
00:54:24,720 --> 00:54:31,280
hosts through in through the year, then that's good. If we were me, I would encourage everyone

548
00:54:31,280 --> 00:54:39,520
holding new hosts to send in lots of shows. If you want the Q2BMT, just to prove that HDR needs

549
00:54:39,520 --> 00:54:45,200
new hosts, I bet that's easily accomplished. But I don't see that changing the nature of reality,

550
00:54:45,280 --> 00:54:54,000
I.e. what it is. So, my reply to that was, well, if you're a pencil and new hosts,

551
00:54:54,000 --> 00:55:02,000
yeah, that was the notification back in 2010. And well, it's hard. We managed not to miss a day

552
00:55:02,000 --> 00:55:08,640
sense, although survival of the show depends on getting you an old host. Yes, that's a realistic

553
00:55:09,120 --> 00:55:15,840
situation. It's an excellent idea encouraging older shows to contribute.

554
00:55:18,000 --> 00:55:23,600
You may want to consider sending them reminders on their own verseries, such as five years since

555
00:55:23,600 --> 00:55:31,120
the last show. If you want the Q2BMT, just to prove that HDR needs new hosts, I bet it's

556
00:55:31,120 --> 00:55:37,360
easily accomplished. In response to that, I said, well, it's a difference between some guy in the

557
00:55:37,360 --> 00:55:46,240
internet and the difference is, between some guy in the internet and the artist, 72,

558
00:55:46,240 --> 00:55:52,320
seem to be on the recording spree. And oh, that's another emergency show. We need to send them

559
00:55:52,320 --> 00:55:58,240
show some shows. So, it's the same reality, but different effects. The two vehicles intended to make

560
00:55:58,240 --> 00:56:04,320
the Q management easier as it will tackle the feast and famine of submissions. Calls for show

561
00:56:04,320 --> 00:56:09,760
work, but there's a problem with it. First, it only reaches a tiny fraction of the community here

562
00:56:09,760 --> 00:56:14,240
and on the mailing list, which is probably the same people anyway. This is on the matrix, but

563
00:56:15,280 --> 00:56:20,720
by filling it in the free slot in the emergency reserve show, we automatically announced

564
00:56:20,720 --> 00:56:25,440
the entire community that there's a free shot slot not being filled. And that we just need to

565
00:56:26,160 --> 00:56:32,800
also, we need another emergency show to replace that one. Secondly, the call for show is

566
00:56:32,880 --> 00:56:38,640
resulting people going to the site to see what the situation is now. And if one's show hosts fills

567
00:56:38,640 --> 00:56:43,840
all the slots with a series they've been working on, then the next person will see a fill queue

568
00:56:43,840 --> 00:56:49,040
and not bother submitting the queue. It's submitting the show. Unfortunately, that happens

569
00:56:49,040 --> 00:56:54,320
on more than one occasion. The two week rule will spread out slots and make the queue management

570
00:56:54,320 --> 00:57:00,800
a lot easier. So, that was the minics one that they posted and my reply to it and then

571
00:57:00,800 --> 00:57:09,520
plateau replied to them. And then I replied to plateau, which I will read. Okay,

572
00:57:11,440 --> 00:57:16,480
we still need more shows from people who have mull posted this year. Okay, what appears to be a

573
00:57:16,480 --> 00:57:22,960
recording spree is in fact people rushing to push shows, rushing to pull something to the queue

574
00:57:22,960 --> 00:57:29,440
to urgently fill a vacant slot. This is undesirable for many reasons. Chasing the queue leads to

575
00:57:29,440 --> 00:57:34,960
burnout. The stress of monitoring and filling up coming slots eats into one's personal time.

576
00:57:34,960 --> 00:57:40,400
And what's supposed to be a hobby becomes a chore. I just want to stop right there.

577
00:57:42,400 --> 00:57:47,520
Dave, when you came aboard, you were doing this. When I came aboard, I was doing this.

578
00:57:47,520 --> 00:57:52,720
Mr. X was doing it for a while. And what I said, and other people down to the age is

579
00:57:52,720 --> 00:57:56,960
having been doing this. Watching the queue every day and then popping in chills to fill it up,

580
00:57:57,040 --> 00:58:02,800
what happens is those people get burnt out and leave the project. So, it's important that

581
00:58:03,760 --> 00:58:09,200
I would like to stress that responsibility for filling this queue does not fall onto the same

582
00:58:09,200 --> 00:58:17,360
people. And I'm calling out some guy in the internet and archer 72 here. These two guys have been

583
00:58:17,360 --> 00:58:23,040
adding shows into the queue to fill vacant slots. And I've been following their discussions on

584
00:58:24,000 --> 00:58:29,520
the matrix panel. And I love the shows. And I don't want them to stop submitting chills. So,

585
00:58:29,520 --> 00:58:35,840
that's why I want the stops submitting shows. But only when the queue is not full. It's not

586
00:58:35,840 --> 00:58:40,320
their responsibility. If you submit one chill a year, you've done your responsibility. You don't

587
00:58:40,320 --> 00:58:47,360
your bit for HPR. And I really appreciate it that they continue to submit chills. But I don't want to

588
00:58:48,160 --> 00:58:53,680
them too guys to burn out. And then I have nobody to go to when I really do need chills.

589
00:58:53,680 --> 00:58:58,640
I hope people understand that. I didn't make it here in my original email. But I'm here back

590
00:58:58,640 --> 00:59:03,440
to what I was saying in the email. And this is about filling vacant slots. We've already had

591
00:59:03,440 --> 00:59:08,720
comments about the quality of shows suffering as a result. Human nature results and people not posting

592
00:59:08,720 --> 00:59:15,120
a show when there are no free slots in the coming month versus when there are slots available.

593
00:59:15,120 --> 00:59:21,760
So, despite both queues containing the same number of shows, we received less shows. Okay. And

594
00:59:21,760 --> 00:59:27,200
other reason, people stop listening to HPR because the feed is full of the one person that they just

595
00:59:27,200 --> 00:59:33,200
happened to not like. And the last most important one to me is HPR is community podcasts. That

596
00:59:33,200 --> 00:59:37,920
means more people need to contribute. It should not be down to the few to keep the project going.

597
00:59:38,800 --> 00:59:46,960
And this is to just go into tattoos come into about moving chills around. Moving chills around

598
00:59:46,960 --> 00:59:51,040
leads to confusion, just satisfaction and complaints. There's why the janitors now always ask

599
00:59:51,040 --> 00:59:56,240
permissions to move chills, which causes the delay in posting all the other shows. Given some

600
00:59:56,240 --> 01:00:02,320
money, as already gone to the effort of recording a show, I personally think it's reasonable to ask

601
01:00:02,400 --> 01:00:08,560
people to scroll down a bit before posting their mech chills. For those who genuinely don't care

602
01:00:09,440 --> 01:00:14,960
when their shows are released, we can add an option to get them to post to the don't care

603
01:00:14,960 --> 01:00:21,040
reserve or emergency queue. So that vacant slots are filled from there. That way the whole

604
01:00:21,040 --> 01:00:27,600
intention is clear from the outset and the janitors know where we stand. We need to at least try this

605
01:00:27,600 --> 01:00:32,480
two week space and think for hosts because I think it will balance out the slow continuous trickle

606
01:00:32,480 --> 01:00:38,320
going out with the bursts of shows that come in. And it will make the actual stage of the queue

607
01:00:38,320 --> 01:00:43,600
more visible. And I think that was about it on that. No, actually those more.

608
01:00:44,960 --> 01:00:50,080
Somebody do Jason Dodds one. See Dave, can you do Jason Dodds and then

609
01:00:51,040 --> 01:01:00,720
Rachel. So Jason Dodds says, my personal thoughts on the topic have turned into me.

610
01:01:01,440 --> 01:01:06,080
Well, this is probably not technically right, not a good thing when discussing amongst hackers

611
01:01:06,080 --> 01:01:11,040
and inspiring hackers. But I think the more rules you put on people who want to contribute shows,

612
01:01:11,040 --> 01:01:16,160
the more you push people off from wanting to contribute. But I do think HP I will get to the

613
01:01:16,480 --> 01:01:24,000
point, either cease or some of those rules or guidelines will have to go. I think as new

614
01:01:24,000 --> 01:01:30,800
hosts become old hosts, they will have a tendency and I still will have a tendency to consider them

615
01:01:30,800 --> 01:01:39,280
and show hosted on HPR. And I like that. I understand that goes against policy and many people do

616
01:01:39,360 --> 01:01:45,040
not like that. My point is that I think it's counter to goal of filling slots. I haven't

617
01:01:45,040 --> 01:01:52,560
caught up on recent email, but I'm half afraid to to fearing that we'll be afraid about how

618
01:01:52,560 --> 01:02:02,400
oh no news has to go. And Rohan, can you do Kevin's first one? Okay, so from Kevin O'Brien,

619
01:02:03,120 --> 01:02:07,200
I'm a strong believer in the value of the life. Actually hold on, that's for the

620
01:02:07,520 --> 01:02:13,280
one. Yeah, you do the second one, please. No, I think it was the right one. No, it wasn't because

621
01:02:13,280 --> 01:02:20,160
it's about the community request input needed by some guy in the internet. So we'll read that

622
01:02:20,160 --> 01:02:31,520
later. Okay, I see. So I went down. Okay, sorry. Sorry, bring forward on my part. I was

623
01:02:31,520 --> 01:02:36,560
not responding to the correct issue here. I followed the guideline of no more than one show

624
01:02:36,640 --> 01:02:41,280
every two weeks for a few years now. And I think it is a good idea. And since the main issue is

625
01:02:41,280 --> 01:02:46,960
that there are not enough shows coming in, it is hard for me to see it as a binding constraint.

626
01:02:46,960 --> 01:02:51,680
If someone has this birth of creativity and records three shows in an afternoon, why is it

627
01:02:51,680 --> 01:02:57,280
bad to tell them to post one every two weeks? I generally record a dozen or more shows over a few

628
01:02:57,280 --> 01:03:03,680
days than upload them in a mass uploading session. Of course, I am retired, so this is a hobby

629
01:03:04,400 --> 01:03:10,880
but I kind of like the two week rule. As it is, I kind of worry that one day I will see messages

630
01:03:10,880 --> 01:03:15,760
on the mailing list saying, when will that guy shut up? But thankfully, that hasn't happened yet,

631
01:03:15,760 --> 01:03:22,880
regards. Excellent. Can did you reply now again? Yeah, I replied to the wrong one as well.

632
01:03:22,880 --> 01:03:28,000
So ignore that. What did the NTs? Oh, I'm essay. Shall I read that?

633
01:03:28,960 --> 01:03:38,560
Yes. So the NTs has, hi. On this, I agree with the majority, that we don't need to change the current

634
01:03:38,560 --> 01:03:45,920
guideline into a hard rule. And it seems like it could accelerate the problem of feeling the queue.

635
01:03:46,640 --> 01:03:52,560
More importantly, I think it would do little to attract more shows by more contributions.

636
01:03:53,120 --> 01:03:58,080
I have fought a lot of things about this. I also have been thinking about what can

637
01:03:58,080 --> 01:04:04,240
say the while ago, which got me thinking about what it seems to be a member of a community project.

638
01:04:04,240 --> 01:04:11,760
I think the process of submitting a show is not very involved, but it does feel quite formal,

639
01:04:11,760 --> 01:04:19,520
which can induce the contributor to feel like they are producing a major work, which can cause delays.

640
01:04:20,400 --> 01:04:27,360
On the other hand, it is important for a contributors first contribution experience to be a positive one.

641
01:04:28,080 --> 01:04:34,720
I think there's probably a wide range of experiences of becoming an HPR host. So there's a wide

642
01:04:34,720 --> 01:04:41,360
range of things people need to help them through that step. For me, I remember, as I stood over a

643
01:04:41,360 --> 01:04:48,720
small pot of porridge, wooden spoon in one hand, phoned in the other. I was really smitten with HPR,

644
01:04:48,800 --> 01:04:54,560
and was very driven to send the show. But I still took a cup, but it still took a couple of

645
01:04:54,560 --> 01:05:00,880
months. We can only imagine how many recorded but unpause the HPR shows are out there.

646
01:05:01,600 --> 01:05:08,720
You could perhaps get another 13 years out of them. Anyway, in the porridge show, I remember that

647
01:05:08,720 --> 01:05:16,160
one by the way, I mentioned some of the shows that captivated me, and ultimately got me to want

648
01:05:17,120 --> 01:05:21,840
and they were by a variety of hosts that don't submit shows at all the time.

649
01:05:22,560 --> 01:05:28,320
I think if HPR would be a show with a small group of rotating hosts, that would be okay.

650
01:05:29,040 --> 01:05:35,360
But it would become much more similar to other shows that I don't listen to.

651
01:05:36,560 --> 01:05:41,520
For me, the key thing with HPR is that you don't know who or what is coming.

652
01:05:42,240 --> 01:05:48,800
Oh gosh, just further. Anyway, I think in the part, we need to understand that HPR's

653
01:05:48,800 --> 01:05:54,960
goal are quite lofty. Actually, and of course, perhaps it will fall at some point.

654
01:05:55,680 --> 01:06:01,280
And it is quite a long run. Also, not always lost when HPR was

655
01:06:01,280 --> 01:06:07,680
fooled, because the archive will live on. With those things in mind, I think it is worth

656
01:06:07,680 --> 01:06:16,560
continuing to aim for an HPR that contains multitudes, many hosts that only contribute sporadically.

657
01:06:17,920 --> 01:06:23,760
We need to accept the risk that comes with that, and agree that they are worth it,

658
01:06:23,760 --> 01:06:26,720
and today, and the day, HPR falls.

659
01:06:27,680 --> 01:06:33,920
Okay, so can you show me spit that up, and you can go turn off that alarm?

660
01:06:34,640 --> 01:06:37,520
There was some review here that in background. Can you continue here?

661
01:06:38,640 --> 01:06:43,840
Somebody else, I can tell. I can take over if you want. Yeah.

662
01:06:46,000 --> 01:06:54,080
So, as for ideas for how to increase listener conversion, and also help fill the queue in another way.

663
01:06:55,440 --> 01:07:00,880
First, rewards for submitting a show. Could we actually offer to send people an HPR sticker

664
01:07:00,960 --> 01:07:05,440
if they are submit the show? Could that be worth doing? Or is it all feasible?

665
01:07:06,000 --> 01:07:11,120
Or could there be some kind of digital thing we could send to people? We would create a bundle

666
01:07:11,120 --> 01:07:15,920
or creative common stuff like a collection of texts about free culture. Yeah, it should be our

667
01:07:15,920 --> 01:07:20,480
contributor handbook, where we would say what we would want to say to all new contributors.

668
01:07:20,480 --> 01:07:25,760
If we had them trapped in a room for hours, how it could be kind of like a catalog. Perhaps

669
01:07:25,760 --> 01:07:31,920
this is something I could apply my developing latex skills to automatically building a

670
01:07:31,920 --> 01:07:38,160
1 million HPDF from the show summaries, et cetera. I'll try to do as a library of stuff.

671
01:07:38,160 --> 01:07:43,680
I'll get in touch with him. Carry on? Yeah. Creating more seamless platforms, this is an

672
01:07:43,680 --> 01:07:49,920
next point, for people to submit shows. I could try to implement that idea of creating an HPR

673
01:07:50,000 --> 01:07:55,920
recording booth in a Matrix channel using Matrix Commander. It could be the HPR confessional

674
01:07:55,920 --> 01:08:02,400
smiley face. Having an excellent having a regular live session on mumble, we can get people

675
01:08:02,400 --> 01:08:07,840
to show up and talk for 24 hours on New Year's Eve. Could it be possible to do it for 30 minutes

676
01:08:07,840 --> 01:08:13,280
a week? We could form a team that rotates staffing that recording session and the focus would

677
01:08:13,280 --> 01:08:18,240
have to be on whoever turns up. That is, if somebody comes to the recording, we start asking

678
01:08:18,240 --> 01:08:23,920
number about them as a tricking them into their how I got into tech show. I also would also do

679
01:08:23,920 --> 01:08:31,120
their best to avoid in name chatter smiley face. Next, consider making a show submission API.

680
01:08:31,120 --> 01:08:35,280
It's our members of the community who would be interested in building a show submission app

681
01:08:35,280 --> 01:08:40,720
that aligns with the goal of getting contributors. I think this has been talked about before

682
01:08:40,720 --> 01:08:45,920
the context of the Linux in-laws asking for it. I think it could be something that eases development

683
01:08:45,920 --> 01:08:52,400
of integrations because if people want to develop an integration, they can do more independently.

684
01:08:52,400 --> 01:08:58,640
Unfortunately, I would have nothing to contribute on this front. Last point reruns once a week

685
01:08:58,640 --> 01:09:03,920
selects a note where the episode from the archive. I read both the old. There's a huge archive

686
01:09:03,920 --> 01:09:09,120
many of us don't know and I have had a great time listening to some old shows, some of the

687
01:09:09,200 --> 01:09:15,920
more venerable among us have mentioned in passing. We could form a small team to select shows.

688
01:09:15,920 --> 01:09:22,000
I think for reposting with people who are interested in randomly listening to old shows to pick

689
01:09:22,000 --> 01:09:27,520
one for the week's rerun is could be called throwback Thursday. I'd be happy to be part of this

690
01:09:27,520 --> 01:09:32,080
team. Thanks for reading D&T. I personally will be opposed to that one.

691
01:09:32,560 --> 01:09:38,640
Customs take up 52 slots. I'm about sharing knowledge. The archive is there for

692
01:09:38,640 --> 01:09:45,200
ever and you can go back and pick those. How if somebody could do a show about shows?

693
01:09:45,200 --> 01:09:51,040
Yeah, absolutely. I'm sort of a meta show. Maybe a, you know, you can call it what throwback

694
01:09:51,040 --> 01:09:58,720
remembrances or something and point them out. Okay, I've completely lost thread where we are now

695
01:09:58,720 --> 01:10:10,640
TNT browning. So we're doing it. Read the one. Yeah, I agree with TNT. You listen to shows like

696
01:10:11,680 --> 01:10:17,680
Ask Noah and they are doing the same. They're not as good editing wise or as funny thing.

697
01:10:18,240 --> 01:10:24,880
I like the shows. Oh, this is, is that, was that the same? I was in that thread but

698
01:10:25,600 --> 01:10:29,680
and this is a free. Yeah. I wasn't quite sure what he's been doing.

699
01:10:29,680 --> 01:10:32,800
Make what he's referencing the last. No, no, it's not one. Yeah.

700
01:10:33,760 --> 01:10:38,880
Maybe the referencing the last point is that what he's dropped. Yeah. I haven't listened to

701
01:10:38,880 --> 01:10:45,280
Ask Noah so I don't know the reference of what you do. There is a, about the simplest

702
01:10:45,280 --> 01:10:50,480
platform thing. I think coming out of this discussion that's more or less is nobody, I think

703
01:10:50,480 --> 01:10:54,800
in the community cares about the queue management as such because she'll just appear

704
01:10:54,800 --> 01:11:02,240
but as admins and people on the matrix town people following the queue for a chase and the queue

705
01:11:02,240 --> 01:11:10,080
is a bit before our very worried about and we get super stressed about there being empty slots.

706
01:11:10,080 --> 01:11:15,520
So I want to take the pressure off that. This is a problem that we've had from day one and continues to be

707
01:11:15,520 --> 01:11:23,440
a problem and the two-week posting thing was an attempt to fix that but I didn't, I don't think I

708
01:11:23,520 --> 01:11:30,560
handle it very well in the original mail but through the process of this at least we know.

709
01:11:32,800 --> 01:11:38,080
Noah, what the community's feelings on it are. Streamlying in the upload process, that's a

710
01:11:38,080 --> 01:11:46,160
very good on that's something I think that we can do. We can put in in the scheduling options so

711
01:11:46,160 --> 01:11:54,160
that you have three options. You pick a slot. You don't care. Are you submitted to the reserve

712
01:11:54,160 --> 01:12:01,120
queue so we can put that as the first option and if somebody says pick a slot then our pick

713
01:12:01,120 --> 01:12:07,040
slot then they're telling us I want my show on this day full stop and we will do that. We will do that

714
01:12:07,040 --> 01:12:12,880
if the slot is free. If not, if they put it into the I don't care schedule or whatever,

715
01:12:12,880 --> 01:12:18,800
we will schedule it according to what we feel is best for the queue and if it goes into the reserve

716
01:12:18,800 --> 01:12:28,000
queue then it goes first in first step. Filling up pick and slots that way. So I'm going in the

717
01:12:28,000 --> 01:12:33,680
internet at arch 72 myself everybody doesn't need to panic about there being a free slot coming up.

718
01:12:33,680 --> 01:12:39,280
We know we have spare ones in the in the hopper ready to go and that that hopefully that just

719
01:12:39,280 --> 01:12:44,320
becomes part of life that we have. I've got their shields coming in and a steady stream going out.

720
01:12:45,920 --> 01:12:52,240
That's all I have to say about by yet. Now moving on to the next top where some guy in the internet

721
01:12:54,480 --> 01:13:03,600
well see that I'll do this out of order because the original request came from me on matrix.

722
01:13:03,680 --> 01:13:07,920
Where I said this issue was posted into the HPR channel on matrix.

723
01:13:10,080 --> 01:13:16,640
Hi some guy in the internet. I love your new show but as a janitor of a few concerns about

724
01:13:16,640 --> 01:13:21,680
carrying them on HPR. The shields represent the problem as they are reporting slash

725
01:13:21,680 --> 01:13:27,360
quoting on someone else's copyrighted work. Therefore it represents a grey area as to if it can

726
01:13:27,360 --> 01:13:32,560
be released onto the great comments or not. We require that you have permission to really just

727
01:13:32,560 --> 01:13:36,880
build your show in and it's entirely that's stuff you need to know permissions.

728
01:13:37,760 --> 01:13:42,640
While some jurisdictions may allow commenting on causing references to other people to work some

729
01:13:42,640 --> 01:13:48,400
may not sort of are opting for certainty. Also we have had experiences with two other

730
01:13:48,400 --> 01:13:54,480
new show series on HPR in the past one by Phoenix which featured out and the other by top geek

731
01:13:54,480 --> 01:14:02,320
to me. That show was syndicated and was moved from HPR following a discussion on the mailing list.

732
01:14:02,640 --> 01:14:08,800
It prompted the rule syndication. At the time there was a question as to the long-term value

733
01:14:08,800 --> 01:14:14,160
of these shows as most of the shows gets half of their audience in the long-tail way after

734
01:14:14,160 --> 01:14:22,000
the show is aired and how well it fits in with the idea of like a moody potter to switch

735
01:14:22,000 --> 01:14:28,400
to very acknowledge. A bit of a change for time so that's just that if you are listening to a new

736
01:14:29,040 --> 01:14:34,240
show that you contact the mail list for our community approval. So who's doing the next one?

737
01:14:35,440 --> 01:14:40,080
Ron, can you do the first one from some guy in the end to the please?

738
01:14:41,040 --> 01:14:46,400
Okay. Hello HPR community. I'm requesting assistance from the HPR community.

739
01:14:46,400 --> 01:14:52,640
The show I produce and upload HPR must be paused until we have the community's input. Nothing too

740
01:14:52,720 --> 01:14:59,680
bad just need more input before continuing. First, I create and release the O'No News on HPR.

741
01:14:59,680 --> 01:15:04,880
It has been brought to my attention that the show's content requires further review and must be

742
01:15:04,880 --> 01:15:10,640
changed to comply with the HPR's community guidelines, including links, gives a link to the

743
01:15:12,000 --> 01:15:18,960
guidelines. Some of the shows contain direct quotes and not all jurisdictions support fair use.

744
01:15:18,960 --> 01:15:25,200
This is a flaw failure on my part and if the show is allowed to continue it must be brought in line

745
01:15:25,200 --> 01:15:31,360
with HPR community guidelines. Secondly, syndication concerns must be addressed.

746
01:15:33,040 --> 01:15:40,720
When I create the HPR news, now O'No News, I did not consider syndication. I had no interest.

747
01:15:40,720 --> 01:15:48,400
Let me be very clear at no point do I plan to seek syndication? I'm not interested. O'No News was

748
01:15:48,400 --> 01:15:54,640
created for the HPR community as a product we can share, enjoy, and participate in without any

749
01:15:54,640 --> 01:16:00,320
limits. It is my way of giving back to the community and that is provided loads of information and

750
01:16:00,320 --> 01:16:06,080
entertainment for me. I'll be releasing a show with more information on the subject soon. Last,

751
01:16:06,080 --> 01:16:12,320
if I must go and let it go, I've enjoyed creating the O'No News but I enjoy HPR more. To show

752
01:16:12,400 --> 01:16:16,880
threatens the community or is it accepted by the community? I have no problem letting go.

753
01:16:16,880 --> 01:16:22,320
The decision has been made and this is a call for all members of the HPR community to weigh in on the matter.

754
01:16:23,120 --> 01:16:28,400
I ask you voice your concerns and or provide any feedback at your earliest convenience. Thanks.

755
01:16:28,960 --> 01:16:31,840
Scotty, some guy on the internet. Do you want to do

756
01:16:33,680 --> 01:16:41,600
likes? Yep, Mike Ray. Mike says, personally I don't like anything that appears on HPR with anything

757
01:16:41,680 --> 01:16:47,760
other than HPR branding. Any recurring cast which seeks its own identity stroke,

758
01:16:47,760 --> 01:16:53,920
label stroke title is in my humble opinion, a parasite. Why not just produce the same content without

759
01:16:53,920 --> 01:17:02,000
the extra layer of branding? Okay, and I replied to this going, the issue about

760
01:17:02,000 --> 01:17:08,560
syndication does not apply to you. I was pointing out other issues with the news show that

761
01:17:08,560 --> 01:17:15,440
arose during the discussion. Sorry for an dismissal understanding. I kind of copy and paste

762
01:17:15,440 --> 01:17:20,160
discussions here for the Matrix channel without individually, so I've asked the Matrix channel to

763
01:17:20,160 --> 01:17:28,640
discuss it here. They met a point on the Matrix channel that the media media quote on free articles,

764
01:17:28,640 --> 01:17:34,880
but in their case they use their own copy to refer to factual events where the news show

765
01:17:34,880 --> 01:17:41,760
here are copying the site content for a while. I mean, that's the reason why I'm pleased that

766
01:17:41,760 --> 01:17:49,040
news story should be paid for and I reference Google because he article where Google is to pay

767
01:17:49,040 --> 01:17:56,800
route where Murdoch for news and Google has to pay Facebook, EU revenue and Microsoft believes

768
01:17:56,880 --> 01:18:04,000
the tech giants should pay for news. So somebody read DNT's one. I can do it.

769
01:18:05,840 --> 01:18:12,960
And there's anybody else wants to sit back and do it, Dave. Okay. So for DNT. Hi, on this, I agree

770
01:18:12,960 --> 01:18:22,080
with the majority that we don't need. Wait, do I just click on that one? I know this matter is mostly

771
01:18:22,080 --> 01:18:30,880
settled from the 29th. Okay. I see it now. Sorry. Hi, I know this matter is mostly settled,

772
01:18:30,880 --> 01:18:35,760
but this is a topic I have a lot of interest in, so if everyone already knows all this,

773
01:18:35,760 --> 01:18:40,880
I thank you for the opportunity to articulate it for myself and sorry if I'm a little verbose.

774
01:18:42,000 --> 01:18:48,160
The way to go would to be have reporting on the facts that you have learned from other sources,

775
01:18:48,240 --> 01:18:53,440
rather than reading the other sources. Since you're not a journalist, you wouldn't even have to

776
01:18:53,440 --> 01:18:58,640
fact check them. If the article includes quotes, you could read some quotes, but you'd have to

777
01:18:58,640 --> 01:19:05,120
avoid quoting the article itself. Essentially, the owner news can't be a substitute for reading

778
01:19:05,120 --> 01:19:10,960
these particular articles and the sense that listening to you read them and the owner news show

779
01:19:10,960 --> 01:19:17,440
does not does the same thing as reading the articles myself. It can serve as a substitute for learning

780
01:19:17,440 --> 01:19:23,040
about the same facts, but if I wanted to read them in that publication, I would so have to go and

781
01:19:23,040 --> 01:19:28,640
read it. There are many newsletters nowadays to cover a variety of things by basically paraphrasing

782
01:19:28,640 --> 01:19:34,880
other publications to propagate the facts. Also, pretty much any time there's a big investigative

783
01:19:34,880 --> 01:19:41,360
news story, one publication breaks it and others reported based on what they learned from that

784
01:19:41,360 --> 01:19:48,720
first publication. After some fact checking, perhaps. In some cases, I think you could quote the

785
01:19:48,720 --> 01:19:55,280
other publication, especially if it is an opinion or analysis piece, because that can be said

786
01:19:55,280 --> 01:20:01,520
be a newsworthy fact. However, again, your piece can't be a viable replacement for the piece you're

787
01:20:01,520 --> 01:20:08,320
quoting, so you'd have to also tell us that while you're quoting what Krebs wrote by adding

788
01:20:08,400 --> 01:20:14,400
your own analysis or perspective. It can't be just just because it was good. For example, you

789
01:20:14,400 --> 01:20:19,360
could report on a certain breach in your own words based on what you've learned from another article

790
01:20:19,360 --> 01:20:24,640
and then you could quote something that Brian Krebs wrote on his blog about it.

791
01:20:25,840 --> 01:20:31,760
If there's some reason what he said in the fact that he said it is itself worthy of reporting on

792
01:20:31,760 --> 01:20:37,760
rather than reporting on the fact via his words. Again, I think the essential thing

793
01:20:38,320 --> 01:20:44,480
is that you can't make the ONO news into a replacement for reading the articles you read on the show.

794
01:20:44,480 --> 01:20:49,280
Therefore, since the articles you read are usually reporting on facts, it should be perfectly

795
01:20:49,280 --> 01:20:54,720
feasible to continue doing the ONO news show by just sticking with the facts and saying them in your

796
01:20:54,720 --> 01:20:59,600
own words and just linking your two sources in your share notes or giving them a shout out.

797
01:21:00,640 --> 01:21:07,120
My understanding of this is based on reading about the U.S. Fair use doctrine, which I know

798
01:21:07,200 --> 01:21:12,800
doesn't necessarily have analogous everywhere, but I do think it reflects pretty universal

799
01:21:12,800 --> 01:21:19,360
understanding of authors' rights and sometimes I think U.S. were just the only country in the world

800
01:21:19,360 --> 01:21:24,960
that need to codify fair use, being the world's most religious society. Nevertheless, I welcome

801
01:21:24,960 --> 01:21:30,960
any corrections to whatever it above, D&T. Retro, can you read the one that's linked in the

802
01:21:30,960 --> 01:21:41,120
chat, please? In the chat, hold on. Hi Scotty, the news is okay, and when I think about it,

803
01:21:41,120 --> 01:21:47,200
I think about something like this to watch. This is what is going on in the Linux world. This is

804
01:21:47,200 --> 01:21:53,360
this also works for larping or rockets, just not something medical or political,

805
01:21:54,000 --> 01:22:00,080
much positive thoughts to you, JVP, JWP. And Dave, can you read that one?

806
01:22:00,080 --> 01:22:07,440
I'm having a ride. Yeah, just a second. Somebody's put some message in the way.

807
01:22:08,880 --> 01:22:18,400
Me, I'm not on a fingers, a whole buttons and doing it. Anyway, yeah, this one, I'm still not in the right place

808
01:22:19,280 --> 01:22:22,960
and we would never have known Dave if you had the first push to talk.

809
01:22:25,200 --> 01:22:34,240
But it's entertaining, watching some guy fall in about and looking at it. So this one is from Scotty

810
01:22:34,240 --> 01:22:40,080
and his guys as young lion. I've made some progress in changing the show format to correct the

811
01:22:40,080 --> 01:22:45,280
copyright issues, quoting articles. It's not much work to correct this issue, but I'm also

812
01:22:45,280 --> 01:22:51,760
contacted some of the sources I draw on youth from for more information concerning their

813
01:22:51,760 --> 01:22:58,080
licenses. I've received emails from the FBI and DEA about their publications. I'm told these

814
01:22:58,080 --> 01:23:05,760
releases are considered public information, but one may not use any of the images, agency loans

815
01:23:05,760 --> 01:23:11,120
or claim to be affiliated with those agencies without written permission. I'm allergic to

816
01:23:11,120 --> 01:23:17,200
prisons so I'll make no such claims. I'm researching other news shows and polishing my craft.

817
01:23:17,200 --> 01:23:25,120
Thank you for the Shannon Morse as a link. Link I will review this. The show does not have

818
01:23:25,120 --> 01:23:30,480
major issues that would cause it to end, but I wanted the community to make that decision. So far,

819
01:23:30,480 --> 01:23:35,040
I've seen positive mentions of the show. This process is healthy. It's more engagement with the

820
01:23:35,040 --> 01:23:40,960
community and a show. Oh no news, we'll benefit from it as well. I would like to hear more from

821
01:23:40,960 --> 01:23:48,320
Mike Ray, perhaps do a show with him on the subject of recurring cast and show labels slash identity.

822
01:23:48,320 --> 01:23:52,560
Thank you for your time, Scotty. See what he did there? See what he did there?

823
01:23:54,560 --> 01:23:56,560
He's smart guy.

824
01:23:56,640 --> 01:24:02,320
And he also says we could rule and do posts with the title if you are weird, I would resist.

825
01:24:02,880 --> 01:24:08,800
The show will wash overhead if you are called like a tsunami. And I think that's is for those.

826
01:24:10,400 --> 01:24:18,320
The community news comments and was the only other thing in the news section rolling down

827
01:24:18,320 --> 01:24:23,440
the events calendar. Do you want to talk about the server move guys?

828
01:24:24,400 --> 01:24:28,400
No, no, this is your baby.

829
01:24:29,120 --> 01:24:41,840
So we are moving servers. Josh needs to need to do some changes to his infrastructure,

830
01:24:42,560 --> 01:24:51,920
which is bringing us along. So we found this to be a highly motivating factor in getting

831
01:24:52,240 --> 01:24:59,920
this switch to the static site. In a working order, at least a working order and good enough to

832
01:25:01,360 --> 01:25:09,760
let us go. Yes. So that will be happening. For some reason I had the 15th of June

833
01:25:09,760 --> 01:25:16,000
stuck in my head, but it sounds like it may be a little sooner than that. We are frankly behind the scenes,

834
01:25:16,320 --> 01:25:24,240
pushing brooms, mopping floors. Talk to is a vault. Yes, lots of duct tape here and there.

835
01:25:24,240 --> 01:25:31,200
A little electrical tape at places, perhaps. Getting things all the all our bits and

836
01:25:31,200 --> 01:25:38,880
bobs and infrastructure moved over to new servers. We're going like said, we're hoping to go to

837
01:25:38,880 --> 01:25:44,080
this. Well, I guess we're not hoping we are going to the hosting the website on the static site.

838
01:25:45,040 --> 01:25:56,000
We're looking to upgrade to the latest version of mailman. So there may be a little bit of disruption

839
01:25:56,000 --> 01:26:02,560
with that. I'm hoping not that there won't be any. We will make sure we don't lose any of the old

840
01:26:02,560 --> 01:26:09,760
archives. It just may be a slightly different place to finding them if you've had things bookmarked

841
01:26:09,760 --> 01:26:19,760
or if you're googling. But generally speaking, that shouldn't miss you. So by this this time,

842
01:26:19,760 --> 01:26:27,760
I guess the next community that we're having will be having a little bit of a post-mortem on

843
01:26:27,760 --> 01:26:34,880
where we are and how things are going. And I guess if things go well, hopefully the mailing,

844
01:26:34,880 --> 01:26:40,320
well, I guess we definitely need to mailing this since that's where people hopefully be complaining

845
01:26:40,320 --> 01:26:48,160
about things. I guess there is matrix in places, but please mostly try, try keeping general comments

846
01:26:48,160 --> 01:26:55,120
and the mailing for our archives just because it's easier for us to keep track of and comment on

847
01:26:55,120 --> 01:27:02,720
during the community news. I know Ken is working furiously and they can get great progress.

848
01:27:03,920 --> 01:27:11,360
I have for some reason decided to volunteer with the mail server. I'm not regretting, but

849
01:27:12,720 --> 01:27:17,520
there's always a lot more to things than you think about when you first starting, like when you

850
01:27:17,840 --> 01:27:23,440
first start. It was nice to hear that out of this. I can go around to you. Yes, yes,

851
01:27:23,440 --> 01:27:29,520
I'm sure they will. I can't think of anything else, can you can take of or Dave that I'm missing

852
01:27:30,560 --> 01:27:37,680
at this point? No, just keep an eye out, bear with us because it's a novel out of work and

853
01:27:37,680 --> 01:27:45,360
we have in the huge amount of spare time. So bear with us as we do this, try and contact us

854
01:27:46,000 --> 01:27:54,400
if you notice stuff and going forward, we will be probably tracking everything on as a

855
01:27:54,400 --> 01:28:01,360
GitHub or a GitHub T issue. So you'll be able to just log your issues there so don't be

856
01:28:02,080 --> 01:28:06,080
to be annoyed if we ask you to do that because then it's on the list for sure for sure.

857
01:28:07,280 --> 01:28:12,480
And that is running now. So actually, you know, you're finding things even now, but particularly

858
01:28:13,280 --> 01:28:19,680
like later in the month, please, if it's a website issue, or even I guess we might need to come up

859
01:28:19,680 --> 01:28:28,480
with a general repository or something for other things just to track issues easier. But for now,

860
01:28:28,480 --> 01:28:36,000
even if there's something and you just go to the site generator repo, you can put an issue and just

861
01:28:36,000 --> 01:28:43,520
talk about whatever failings you find. I think it is very exciting at project you're doing here

862
01:28:43,520 --> 01:28:49,040
and I love to hear about it. Just one question about that, I don't know if I missed it or not,

863
01:28:49,040 --> 01:28:57,840
is there how to say a prototype or something like that running on a URL or is it just that you

864
01:28:57,840 --> 01:29:06,240
would have to build it by yourself if to repo? No, no, it's the, yeah, they currently go to

865
01:29:06,240 --> 01:29:10,320
HackerPublicRadio.com. If you really want to see the bleeding edge of the move,

866
01:29:11,520 --> 01:29:18,000
because that is where everything is at the moment and then HackerPublicRadio.org will switch.

867
01:29:18,800 --> 01:29:26,800
So we will talk more about the idea behind this is that anybody can take the static site and

868
01:29:26,800 --> 01:29:33,360
host it on their own site and then we will round up and DNS over to your site as well as the

869
01:29:33,360 --> 01:29:39,200
HPR site. That's the goal and there should be, we're not going to do that straight out the gaze,

870
01:29:39,200 --> 01:29:45,840
but in six months to a year plan to do that. And the reason we have lots of bug fixes to do

871
01:29:45,840 --> 01:29:53,200
between them. Right, and you can actually, to sort of see that effect, you can, if you go to

872
01:29:53,200 --> 01:30:05,040
HPR.corning.us at htbs or I think, and then I think hobbypublicradio.org is a mirror also. So

873
01:30:05,040 --> 01:30:09,680
just sort of see it in effect. Those are the statically generated sites currently.

874
01:30:11,040 --> 01:30:17,440
Can we put that links into the show notes? No, no, let's, let's not do that. It just, we're too busy

875
01:30:18,160 --> 01:30:24,640
moving the site, on the site moves the site and move. Yeah, okay, I cannot, over a stage,

876
01:30:24,640 --> 01:30:31,840
how busy we are with this. It is, any free time we have, we're working on the website. So leave

877
01:30:31,840 --> 01:30:38,240
us be, if there are bugs, making all of them. Yeah, caused by next month, it'll be over and then

878
01:30:38,240 --> 01:30:47,280
you can answer all the questions. All right. Okay, so server move, connecting hold, hold, hold. So

879
01:30:47,840 --> 01:30:55,040
I'm coming up during that whole conversation about the two week thing was, we're trying to fill

880
01:30:55,040 --> 01:30:59,200
the queue and we're trying to fill the queue with new hosts, but what about the old hosts? Why?

881
01:31:01,040 --> 01:31:06,720
We have 400 or more hosts that have come to the trouble of submitting a show. Why have this stopped?

882
01:31:08,240 --> 01:31:14,480
In two cases that we know have passed away. So that's a good reason. But everybody else,

883
01:31:14,480 --> 01:31:20,240
why have this stopped posting shows? I don't want to send out the mass mailing to people because

884
01:31:22,240 --> 01:31:27,040
now is not a good time to do that anyway, but would people be open to the idea

885
01:31:27,600 --> 01:31:33,280
or being contacted maybe on your show anniversary or maybe our cheerleaders

886
01:31:34,240 --> 01:31:45,200
in doing the retro look interview a host from days of your and discuss their shows with them

887
01:31:45,200 --> 01:31:52,960
as a new show itself. So ideas there, we have this pool of people who did at one point get

888
01:31:52,960 --> 01:31:59,360
all there are some submissive show. Why are we not able to get those the more shows from people?

889
01:32:00,320 --> 01:32:08,400
And then, did you talk about, sorry, what? I know now isn't the time for maybe the

890
01:32:08,400 --> 01:32:13,920
janitors, but other people are not saying we do a mass mailing, but maybe I don't know, you know,

891
01:32:13,920 --> 01:32:20,720
I know there's like poles and things in for different matrix and stuff that somebody could

892
01:32:20,720 --> 01:32:25,520
maybe take on themselves. And I think it would be eventually maybe not this month, but

893
01:32:25,600 --> 01:32:31,040
thinking about it next month, doing some kind of like figuring out that, asking that question,

894
01:32:31,040 --> 01:32:36,240
figuring out the best way to ask that question is like, what, you know, have you just moved on, have you

895
01:32:37,920 --> 01:32:44,160
hadn't listened to HBR and, you know, five year, you know, what sort of, what are the barriers

896
01:32:44,160 --> 01:32:50,880
to older host producing a show or? Yeah, and I don't want to mass mail people because that's

897
01:32:50,960 --> 01:32:57,920
very impersonal and people will see it as spam, but a targeted email to, hey, I like to show

898
01:32:57,920 --> 01:33:04,000
about, you know, the scanner-led thing and, you know, I just realized that I needed to

899
01:33:05,280 --> 01:33:10,320
that, I came across your show for some reason, either it's your anniversary or whatever,

900
01:33:11,600 --> 01:33:18,400
you know, any idea why, where you consider doing a show or basically a one-to-one question,

901
01:33:18,400 --> 01:33:23,200
rather than a mass mailing list, it's a lot more likely that you're going to get positive feedback

902
01:33:23,200 --> 01:33:29,760
as opposed to if we send out a mail list, people will, will, I guarantee you this unsubscribe from

903
01:33:29,760 --> 01:33:36,800
the mail list as a result and will not want to be contacted anymore. And don't forget the files that

904
01:33:36,800 --> 01:33:46,240
already lay on your heart drive and the modern podcast player will jump any empty spaces in it or

905
01:33:46,240 --> 01:33:51,520
such, so you don't need to polish them, you could just send it in the podcast player does the rest.

906
01:33:52,400 --> 01:34:01,120
So I was just going to mention that in the last month, we cleaned up, I believe, all of the

907
01:34:01,120 --> 01:34:07,120
Windows 1252 characters, Latin ones, they're also called, from the database and replace them with

908
01:34:07,120 --> 01:34:14,400
UTF8, UD code stuff. So I can't see anything left over, but anybody does spot anything like that,

909
01:34:14,480 --> 01:34:21,120
and characters sent issues, let me know and we'll fix them to. Okay, with that,

910
01:34:21,120 --> 01:34:26,400
shooting some more, for a little bit of exciting episode of Agar,

911
01:34:26,400 --> 01:34:42,240
hacker, public, radio, you have been listening to hacker public radio, at hacker public radio.org.

912
01:34:42,240 --> 01:34:48,240
Today's show was contributed by a HBR this night like yourself, if you ever thought of recording

913
01:34:48,240 --> 01:34:55,760
podcast, click on our contribute link to find out how easy it means, hosting for HBR has been

914
01:34:55,840 --> 01:35:02,560
kindly provided by an onsthost.com, the internet archive and our synced.net.

915
01:35:02,560 --> 01:35:07,440
On the satellite stages, today's show is released on our creative comments,

916
01:35:07,440 --> 01:35:14,720
attribution 4.0 international license.